rcDot1agCfmMepTable

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.

MIB

RAISECOM-DOT1AG-MIB

OID

.1.3.6.1.4.1.8886.6.1.32.1.7.1

Type

table

Status

current

Parent

rcDot1agCfmMep

Siblings

2

Children

1