Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"prvtCfmMepTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"PrvtCfmMepEntry",
"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.18). 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) Set prvtCfmMepTransmitLbmStatus to true 2) Set the target by: a) target mep - configue prvtCfmMepTransmitLbmDestIsMepId on true and then configure prvtCfmMepTransmitLbmDestMepId with the remote mep id b) target mac - configue prvtCfmMepTransmitLbmDestIsMepId on false and then configure prvtCfmMepTransmitLbmDestMacAddress with the remote device mac address 3) Setup the different data to be sent (number of messages, optional TLVs,...). 4) Record the current values of prvtCfmMepLbrIn, prvtCfmMepLbrInOutOfOrder, and prvtCfmMepLbrBadMsdu. 6) Change prvtCfmMepTransmitLbmStatus value to false to initiate transmission of Loopback messages. 7) Check the value of prvtCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) If prvtCfmMepTransmitLbmInfinite is set to false you can monitor the value of prvtCfmMepTransmitLbmRemainingMessages. When it reaches 0, the last LBM has been transmitted and the operation is finished. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) If prvtCfmMepTransmitLbmInfinite is set to true you must stop the operation yourself by setting prvtCfmMepTransmitLbmStatus to true. 10) Compare prvtCfmMepLbrIn, prvtCfmMepLbrInOutOfOrder, and prvtCfmMepLbrBadMsdu 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. Upon successfully initiating the transmission, the variables pvrtCfmMepTransmitLtmSeqNumber and prvtCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the prvtCfmLtrTable.\"",
"REFERENCE",
"\"802.1ag clauses 12.14.7 and 19.2\"",
"::=",
"{",
"prvtCfmMep",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"PrvtCfmMepEntry"
]
],
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.18). 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) Set prvtCfmMepTransmitLbmStatus to true 2) Set the target by: a) target mep - configue prvtCfmMepTransmitLbmDestIsMepId on true and then configure prvtCfmMepTransmitLbmDestMepId with the remote mep id b) target mac - configue prvtCfmMepTransmitLbmDestIsMepId on false and then configure prvtCfmMepTransmitLbmDestMacAddress with the remote device mac address 3) Setup the different data to be sent (number of messages, optional TLVs,...). 4) Record the current values of prvtCfmMepLbrIn, prvtCfmMepLbrInOutOfOrder, and prvtCfmMepLbrBadMsdu. 6) Change prvtCfmMepTransmitLbmStatus value to false to initiate transmission of Loopback messages. 7) Check the value of prvtCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) If prvtCfmMepTransmitLbmInfinite is set to false you can monitor the value of prvtCfmMepTransmitLbmRemainingMessages. When it reaches 0, the last LBM has been transmitted and the operation is finished. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) If prvtCfmMepTransmitLbmInfinite is set to true you must stop the operation yourself by setting prvtCfmMepTransmitLbmStatus to true. 10) Compare prvtCfmMepLbrIn, prvtCfmMepLbrInOutOfOrder, and prvtCfmMepLbrBadMsdu 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. Upon successfully initiating the transmission, the variables pvrtCfmMepTransmitLtmSeqNumber and prvtCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the prvtCfmLtrTable."
],
[
"REFERENCE",
"802.1ag clauses 12.14.7 and 19.2"
],
null,
null,
null
]
}