Configuring a Maintenance Endpoint
To configure the maintenance endpoint, include the mep mep-id statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name] hierarchy level.
Enabling Maintenance Endpoint Automatic Discovery
You can enable the MEP to accept continuity check messages from all remote MEPs of the same maintenance association.
To configure automatic discovery, include the auto-discovery statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id] hierarchy level.
Configuring the Maintenance Endpoint Direction
You can specify the direction in which CFM packets are transmitted for the MEP.
Direction up continuity check messages (CCMs) are transmitted out of every logical interface that is part of the same bridging or VPLS instance except for the interface configured on this MEP.
Direction down CCMs are transmitted only out of the interface configured on this MEP.
 | Note: Ports in the Spanning Tree Protocol (STP) blocking state do not block CFM packets destined to a down MEP. Ports in an STP blocking state without the continuity check protocol configured do block CFM packets. |
To configure the MEP direction, include the direction statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id] hierarchy level.
Configuring the Maintenance Endpoint Interface
You must specify the interface to which the MEP is attached. It can be a physical interface, logical interface, or trunk interface.
On MX Series routers, you can enable the MEP on a specific VLAN of a trunk interface.
To configure the interface, include the interface interface-name statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id] hierarchy level.
MEP Interface Configuration
This example shows the MEP interface configuration statements:
Configuring the Maintenance Endpoint Priority
You can specify the IEEE 802.1 priority bits that are used by continuity check and link trace messages.
To configure the priority, include the priority statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id] hierarchy level.
Configuring the Maintenance Endpoint Lowest Priority Defect
You can specify the lowest priority defect that is allowed to generate a fault alarm. This configuration determines whether to generate a fault alarm whenever it detects a defect. This configuration is done at the MEP level.
To configure the lowest priority defect, include the lowest-priority-defect <options> statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id] hierarchy level.
Table 1 describes the available lowest priority defect options.
Table 1: Lowest Priority Defect Options
Option | Description |
|---|---|
all-defects | Allows all defects. |
err-xcon | Allows only erroneous CCM and cross-connect CCM defects. |
mac-rem-err-xcon | Allows only MAC, not receiving CCM, erroneous CCM, and cross-connect defects. |
no-defect | Allows no defect. |
rem-err-xcon | Allows only not receiving CCM, erroneous CCM, and cross-connect CCM defects. |
xcon | Allows only cross-connect CCM defects. |
The following configuration example shows mac-rem-err-xcon as the lowest priority defect:
Configuring a Remote Maintenance Endpoint
You can configure a remote MEP from which CCM messages are expected. If autodiscovery is not enabled, the remote MEP must be configured under the mep statement. If the remote MEP is not configured under the mep statement, the CCMs from the remote MEP are treated as errors.
To configure the remote MEP, include the remote-mep statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id] hierarchy level.
Configuring a Remote Maintenance Endpoint Action Profile
You can specify the name of the action profile to use for the remote MEP.
To configure the action profile, include the action-profile profile-name statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-association ma-name mep mep-id remote-mep mep-id] hierarchy level. The profile must already be defined at the [edit protocols oam ethernet connectivity-fault-management] hierarchy level.
