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.19).
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. Upon
successfully initiating the transmission, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.
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.19).
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. Upon
successfully initiating the transmission, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.
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.19).
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. Upon
successfully initiating the transmission, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.
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.19).
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. Upon
successfully initiating the transmission, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.
Parsed from file IEEE8021-CFM-MIB.my.txt
Company: None
Module: IEEE8021-CFM-MIB
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.19).
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. Upon
successfully initiating the transmission, the variables
dot1agCfmMepTransmitLtmSeqNumber and
dot1agCfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
dot1agCfmLtrTable.
Parsed from file IEEE8021-CFM-MIB.mib
Module: IEEE8021-CFM-MIB
dot1agCfmMepTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMepEntry ACCESS not-accessible STATUS mandatory 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.19). 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. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable." REFERENCE "802.1ag clauses 12.14.7 and 19.2" ::= { dot1agCfmMep 1 }
Vendor: Cisco Systems
Module: IEEE8021-CFM-MIB (IEEE8021-CFM-MIB-V1SMI.my)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
dot1agCfmMepTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMepEntry 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.19). 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. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable. " REFERENCE "802.1ag clauses 12.14.7 and 19.2" ::= { dot1agCfmMep 1 }
dot1agCfmMepTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMepEntry 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.19). 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. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable. " REFERENCE "802.1ag clauses 12.14.7 and 19.2" ::= { dot1agCfmMep 1 }
dot1agCfmMepTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMepEntry 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.19). 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. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable. " REFERENCE "802.1ag clauses 12.14.7 and 19.2" ::= { dot1agCfmMep 1 }
dot1agCfmMepTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMepEntry 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.19). 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. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable. " REFERENCE "802.1ag clauses 12.14.7 and 19.2" ::= { dot1agCfmMep 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.8.1.7.1.1 | dot1agCfmMepEntry | 51 | 51 | The MEP table entry |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.8.1.7.2 | dot1agCfmLtrTable | 1 | 22 | This table extends the MEP table and contains a list of Linktrace replies received by a specific MEP in response to a linktrace m… |
| 1.3.111.2.802.1.1.8.1.7.3 | dot1agCfmMepDbTable | 1 | 13 | The MEP Database. A database, maintained by every MEP, that maintains received information about other MEPs in the Maintenance Do… |