OID reference

rcDot1agCfmMepTable

1.3.6.1.4.1.8886.6.1.32.1.7.1

Description

The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.8886.6.1.32.1.7 (rcDot1agCfmMep)
Node code
1
Node name
rcDot1agCfmMepTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.8886.6.1.32.1.7.1
URN notation
urn:oid:1.3.6.1.4.1.8886.6.1.32.1.7.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 8886 6 1 32 1 7 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMep(7) rcDot1agCfmMepTable(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/8886/6/1/32/1/7/1
  • /ISO/Identified-Organization/6/1/4/1/8886/6/1/32/1/7/1
  • /ISO/3/6/1/4/1/8886/6/1/32/1/7/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/enterprise/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/enterprise/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/enterprises/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/enterprises/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/enterprises/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/org/dod/internet/private/enterprise/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/org/dod/internet/private/enterprise/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/org/dod/internet/private/enterprise/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • /iso/org/dod/internet/private/enterprises/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMep/rcDot1agCfmMepTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF RcDot1agCfmMepEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

rcDot1agCfmMepTable
OBJECT-TYPE
    SYNTAX      SEQUENCE OF RcDot1agCfmMepEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "The Maintenance Association End Point (MEP) table.

        Each row in the table represents a different MEP.  A MEP is
        an actively managed CFM entity, associated with a specific
        DSAP of a Service Instance, which can generate and receive
        CFM PDUs and track any responses.  It is an end point of a
        single Maintenance Association, and is an endpoint of a
        separate Maintenance Entity for each of the other MEPs in
        the same Maintenance Association (802.1ag clause 3.17).

        This table uses three indices. The first two indices are the
        indices of the Maintenance Domain and MA tables, the reason
        being that a MEP is always related to an MA and Maintenance
        Domain.

        The MEP table also stores all the managed objects for sending
        LBM and LTM.

        *LBM Managed objects

        LBM Managed objects in the MEP table 
        enables the management entity to initiate
        transmission of Loopback messages.  It will signal the MEP
        that it should transmit some number of Loopback messages
        and detect the detection (or lack thereof) of the
        corresponding Loopback messages.
 
        Steps to use entries in this table:

        1) Wait for rcDot1agCfmMepTransmitLbmStatus value to be
           true.  To do this do this sequence:
           a. an SNMP GET for both SnmpSetSerialNo and
              rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP
              PDU).
           b. Check if value for rcDot1agCfmMepTransmitLbmStatus is true.
              - if not, wait x seconds, go to step a above.
              - if yes, save the value of SnmpSetSerialNo and go
                to step 2) below
        2) Change rcDot1agCfmMepTransmitLbmStatus value from true to
           false to ensure no other management entity will use
           the service. In order to not disturb a possible other NMS
           do this by sending an SNMP SET for both SnmpSetSerialNo 
           and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP
           PDU,  and make sure SNmpSetSerialNo is the first varBind).
           For the SnmpSetSerialNo varBind, use the value that you
           obtained in step 1)a.. This ensures that two cooperating
           NMSes will not step on each others toes.
        3) Setup the different data to be sent (number of messages,
           optional TLVs,...), except do not set
           rcDot1agCfmMepTransmitLbmMessages.
        4) Record the current values of rcDot1agCfmMepLbrIn,
           rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu.
        6) Set rcDot1agCfmMepTransmitLbmMessages to a non-zero value to
           initiate transmission of Loopback messages.
        7) Check the value of rcDot1agCfmMepTransmitLbmResultOK to
           find out if the operation was successfully initiated or
           not.
        8) Monitor the value of rcDot1agCfmMepTransmitLbmMessages.
           When it reaches 0, the last LBM has been transmitted.
           Wait an additional 5 seconds to ensure that all LBRs have
           been returned.
        9) Compare rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder,
           and rcDot1agCfmMepLbrBadMsdu to their old values from step
           4, above, to get the results of the test.
       10) Change the rcDot1agCfmMepTransmitLbmStatus value back to
           true to allow other management entities to use the table.

        *LTM Managed objects
        The LTM Managed objects in the MEP table are used in a manner
        similar to that described for LBM transmission, above, except
        transmission is initiated by writing a value to the
        rcDot1agCfmMepTransmitLtmFlags object.  Upon
        successfully initiating the transmission, the variables
        rcDot1agCfmMepTransmitLtmSeqNumber and
        rcDot1agCfmMepTransmitLtmEgressIdentifier return the information
        required to recover the results of the LTM from the
        rcDot1agCfmLtrTable.
       "
    REFERENCE
       "802.1ag clauses 12.14.7 and 19.2"
    ::= { rcDot1agCfmMep 1 }

Meaning

Descriptions

1 unique

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

The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.17). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain. The MEP table also stores all the managed objects for sending LBM and LTM. *LBM Managed objects LBM Managed objects in the MEP table enables the management entity to initiate transmission of Loopback messages. It will signal the MEP that it should transmit some number of Loopback messages and detect the detection (or lack thereof) of the corresponding Loopback messages. Steps to use entries in this table: 1) Wait for rcDot1agCfmMepTransmitLbmStatus value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for rcDot1agCfmMepTransmitLbmStatus is true. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change rcDot1agCfmMepTransmitLbmStatus value from true to false to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the different data to be sent (number of messages, optional TLVs,...), except do not set rcDot1agCfmMepTransmitLbmMessages. 4) Record the current values of rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu. 6) Set rcDot1agCfmMepTransmitLbmMessages to a non-zero value to initiate transmission of Loopback messages. 7) Check the value of rcDot1agCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) Monitor the value of rcDot1agCfmMepTransmitLbmMessages. When it reaches 0, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) Compare rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. 10) Change the rcDot1agCfmMepTransmitLbmStatus value back to true to allow other management entities to use the table. *LTM Managed objects The LTM Managed objects in the MEP table are used in a manner similar to that described for LBM transmission, above, except transmission is initiated by writing a value to the rcDot1agCfmMepTransmitLtmFlags object. Upon successfully initiating the transmission, the variables rcDot1agCfmMepTransmitLtmSeqNumber and rcDot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the rcDot1agCfmLtrTable.

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 · 1 source

Description 1

rcDot1agCfmMepTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: rcDot1agCfmMepTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rcDot1agCfmMepTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "RcDot1agCfmMepEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.17). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain. The MEP table also stores all the managed objects for sending LBM and LTM. *LBM Managed objects LBM Managed objects in the MEP table enables the management entity to initiate transmission of Loopback messages. It will signal the MEP that it should transmit some number of Loopback messages and detect the detection (or lack thereof) of the corresponding Loopback messages. Steps to use entries in this table: 1) Wait for rcDot1agCfmMepTransmitLbmStatus value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for rcDot1agCfmMepTransmitLbmStatus is true. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change rcDot1agCfmMepTransmitLbmStatus value from true to false to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the different data to be sent (number of messages, optional TLVs,...), except do not set rcDot1agCfmMepTransmitLbmMessages. 4) Record the current values of rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu. 6) Set rcDot1agCfmMepTransmitLbmMessages to a non-zero value to initiate transmission of Loopback messages. 7) Check the value of rcDot1agCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) Monitor the value of rcDot1agCfmMepTransmitLbmMessages. When it reaches 0, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) Compare rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. 10) Change the rcDot1agCfmMepTransmitLbmStatus value back to true to allow other management entities to use the table. *LTM Managed objects The LTM Managed objects in the MEP table are used in a manner similar to that described for LBM transmission, above, except transmission is initiated by writing a value to the rcDot1agCfmMepTransmitLtmFlags object. Upon successfully initiating the transmission, the variables rcDot1agCfmMepTransmitLtmSeqNumber and rcDot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the rcDot1agCfmLtrTable. \"",
    "REFERENCE",
    "\"802.1ag clauses 12.14.7 and 19.2\"",
    "::=",
    "{",
    "rcDot1agCfmMep",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "RcDot1agCfmMepEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.17). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain. The MEP table also stores all the managed objects for sending LBM and LTM. *LBM Managed objects LBM Managed objects in the MEP table enables the management entity to initiate transmission of Loopback messages. It will signal the MEP that it should transmit some number of Loopback messages and detect the detection (or lack thereof) of the corresponding Loopback messages. Steps to use entries in this table: 1) Wait for rcDot1agCfmMepTransmitLbmStatus value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for rcDot1agCfmMepTransmitLbmStatus is true. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change rcDot1agCfmMepTransmitLbmStatus value from true to false to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and rcDot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the different data to be sent (number of messages, optional TLVs,...), except do not set rcDot1agCfmMepTransmitLbmMessages. 4) Record the current values of rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu. 6) Set rcDot1agCfmMepTransmitLbmMessages to a non-zero value to initiate transmission of Loopback messages. 7) Check the value of rcDot1agCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) Monitor the value of rcDot1agCfmMepTransmitLbmMessages. When it reaches 0, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) Compare rcDot1agCfmMepLbrIn, rcDot1agCfmMepLbrInOutOfOrder, and rcDot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. 10) Change the rcDot1agCfmMepTransmitLbmStatus value back to true to allow other management entities to use the table. *LTM Managed objects The LTM Managed objects in the MEP table are used in a manner similar to that described for LBM transmission, above, except transmission is initiated by writing a value to the rcDot1agCfmMepTransmitLtmFlags object. Upon successfully initiating the transmission, the variables rcDot1agCfmMepTransmitLtmSeqNumber and rcDot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the rcDot1agCfmLtrTable."
    ],
    [
      "REFERENCE",
      "802.1ag clauses 12.14.7 and 19.2"
    ],
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: RAISECOM-DOT1AG-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'LLDP-MIB': ['LldpChassisId', 'LldpChassisIdSubtype', 'LldpPortId', 'LldpPortIdSubtype'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeInterval', 'TimeStamp', 'RowStatus', 'TruthValue', 'MacAddress', 'TDomain', 'TAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Counter32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanIdOrNone', 'VlanId'], 'IEEE8021-CFM-MIB': ['Dot1agCfmMaintDomainNameType', 'Dot1agCfmMaintDomainName', 'Dot1agCfmIngressActionFieldValue', 'Dot1agCfmMaintAssocNameType', 'Dot1agCfmMaintAssocName', 'Dot1agCfmMDLevel', 'Dot1agCfmMDLevelOrNone', 'Dot1agCfmMpDirection', 'Dot1agCfmPortStatus', 'Dot1agCfmInterfaceStatus', 'Dot1agCfmHighestDefectPri', 'Dot1agCfmLowestAlarmPri', 'Dot1agCfmMepId', 'Dot1agCfmMepIdOrZero', 'Dot1agCfmMhfCreation', 'Dot1agCfmIdPermission', 'Dot1agCfmCcmInterval', 'Dot1agCfmFngState', 'Dot1agCfmRelayActionFieldValue', 'Dot1agCfmEgressActionFieldValue', 'Dot1agCfmRemoteMepState', 'Dot1afCfmIndexIntegerNextFree', 'Dot1agCfmMepDefects', 'dot1agCfmMepHighestPrDefect', 'Dot1agCfmConfigErrors', 'Dot1agCfmPbbComponentIdentifier'], 'RAISECOM-BASE-MIB': ['iscomSwitch']}
    · Download RAISECOM-DOT1AG-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.8886)

Gao Lei

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.32.1.7.1.1 rcDot1agCfmMepEntry4545

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.32.1.7.2 rcDot1agCfmLtrTable122
1.3.6.1.4.1.8886.6.1.32.1.7.3 rcDot1agCfmMepDbTable112