dot1agCfmMepTable

The Maintenance Association Endpoint (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 endpoint 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 (3.132).
          
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 dot1agCfmMepTransmitLbmStatus value to be
   false.  To do this do this sequence:
   a. an SNMP GET for both SnmpSetSerialNo and
      dot1agCfmMepTransmitLbmStatus objects (in same SNMP
      PDU).
   b. Check if value for dot1agCfmMepTransmitLbmStatus is false.
      - 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 dot1agCfmMepTransmitLbmStatus value from false to
   true 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 dot1agCfmMepTransmitLbmStatus 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.
   Setting this MIB object does not set the corresponding
   LBIactive state machine variable.
3) Setup the different data to be sent (number of messages,
   optional TLVs,...), except do not set
   dot1agCfmMepTransmitLbmMessages.
4) Record the current values of dot1agCfmMepLbrIn,
   dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu.
6) Set dot1agCfmMepTransmitLbmMessages to a non-zero value to
   initiate transmission of Loopback messages.
   The dot1agCfmMepTransmitLbmMessages indicates the
   number of LBMs to be sent and is not decremented as
   loopbacks are actually sent. dot1agCfmMepTransmitLbmMessages
   is not equivalent to the LBMsToSend state machine variable.
7) Check the value of dot1agCfmMepTransmitLbmResultOK to
   find out if the operation was successfully initiated or
   not.
8) Monitor the value of dot1agCfmMepTransmitLbmStatus.
   When it is reset to false, the last LBM has been transmitted.
   Wait an additional 5 seconds to ensure that all LBRs have
   been returned.
9) Compare dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder,
   and dot1agCfmMepLbrBadMsdu to their old values from step
   4, above, to get the results of the test.
          
*LTM Managed objects
The LTM Managed objects in the MEP table are used in a manner
similar to that described for LBM transmission, above. A SET
operation to the variable dot1agCfmMepTransmitLtmFlags
triggers the transmission of an LTM. Then, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.

MIB

IEEE8021-CFM-MIB

OID

.1.3.111.2.802.1.1.8.1.7.1

Type

table

Status

current

Parent

dot1agCfmMep

Siblings

2

Children

1