mep mep-id (MA view)

Function

The mep mep-id command creates a maintenance association end point (MEP).

The undo mep mep-id command deletes a MEP.

By default, no MEP is created on a device.

Format

mep mep-id mep-id { vlan | { interface { interface-name | interface-type interface-number } [ vlan vlan-id | pe-vid pe-vid-value ce-vid ce-vid-value ] { inward | outward } } | { peer-ip peer-address [ vc-id vc-id ] [ mac group-mac ] { inward | outward } } }

undo mep mep-id mep-id [ vlan | { interface { interface-name | interface-type interface-number } [ vlan vlan-id | pe-vid pe-vid-value ce-vid ce-vid-value ] { inward | outward } } | { peer-ip peer-address [ vc-id vc-id ] [ mac group-mac ] { inward | outward } } ]

Parameters

Parameter	Description	Value
mep-id	Specifies the ID of a MEP. The ID identifies a MEP.	The value is an integer ranging from 1 to 8191
vlan	Indicates a VLAN-based MEP.	-
vlan vlan-id	Specifies a VLAN to which an interface belongs.	The value is an integer ranging from 1 to 4094.
interface interface-type interface-number	Specifies the type and number of an interface.	-
pe-vid pe-vid-value	Specifies the VLAN ID of a provider edge (PE).	The value is an integer ranging from 1 to 4094.
ce-vid ce-vid-value	Specifies the VLAN ID of a customer edge (CE).	The value is an integer ranging from 1 to 4094.
inward	Indicates an inward-facing MEP.	-
outward	Indicates an outward-facing MEP.	-
peer-ip peer-address	Specifies a peer IP address.	The value is in dotted decimal notation.
vc-id vc-id	Specifies a VC ID.	The value is an integer ranging from 1 to 4294967295.
mac group-mac	Specifies a MAC address.	The value is a non-all-zero unicast MAC address, in the format of H-H-H.

Views

MA view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
y1731	write

Usage Guidelines

Usage Scenario

The mep mep-id command can be used to create MEPs that define a connectivity fault management (CFM) area. CFM supports continuity check (CC), loopback (LB), and link trace (LT) functions on end-to-end (E2E) links between MEPs.

MEPs are classified into the following types:

Inward-facing MEP: sends packets to other interfaces on the same device.
Outward-facing MEP: sends packets out of the interface on which the MEP is configured.

Prerequisites

An MD and an MA have been configured using the cfm md and ma commands, respectively.

The MA has been bound to a virtual leased line (VLL) or virtual private LAN service (VPLS) using the map command.

A QinQ VLAN tag termination sub-interface has been configured using the qinq termination pe-vid command in the case of QinQ VLAN tag termination sub-interface access.

Follow-up Procedure

Run the mep ccm-send enable command to enable the MEP in the MA to send continuity check messages (CCMs).

Precautions

Specifications of MEPs to be created in an MA are as follows:

VLAN-based and interface-based MEPs are mutually exclusive. Common inward-based and outward-facing MEPs are mutually exclusive.
A single outward-facing interface-based MEP can be created. Multiple inward-facing interface-based MEPs can be created on a device. An interface supports only one inward-facing interface-based MEP.
Only one VLAN-based MEP can be created.
The maximum number of MEPs that can be created varies according to interface board types and router models. For details about specifications, see the specification description of a specific interface board or router.
Precautions for creating a MEP in an MA are as follows:
An MA in which an inward-facing interface-based MEP is to be created must have been associated with a service (for example, a VLAN, L2VC, or VSI), and the service must have been configured on the interface on which the MEP is to be created.
An MA does not need to be associated with a service if an outward-facing interface-based MEP is to be created in the MA. If the MA has been associated with a service, the service must be configured on the interface on which the MEP is to be created.
The MA must be associated with a VLAN if a VLAN-based MEP is to be created in the MA.
An MA in which a PW-based MEP is to be created must have been associated with a service (for example, a VSI), and the specified PW must belong to the service.

Example

# Create an inward-facing MEP with an ID of 1 based on the PW with VSI 1 and the peer IP address 2.2.2.2 in the MA named

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] mpls l2vpn
[*HUAWEI-l2vpn] quit
[*HUAWEI] vsi vsi1
[*HUAWEI-vsi-vsi1] pwsignal ldp
[*HUAWEI-vsi-vsi1-ldp] vsi-id 10
[*HUAWEI-vsi-vsi1-ldp] peer 2.2.2.2
[*HUAWEI-vsi-vsi1-ldp] quit
[*HUAWEI-vsi-vsi1] quit
[*HUAWEI] cfm enable
[*HUAWEI] cfm md md1
[*HUAWEI-md-md1] ma ma1
[*HUAWEI-md-md1-ma-ma1] map vsi vsi1
[*HUAWEI-md-md1-ma-ma1] mep mep-id 1 peer-ip 2.2.2.2 inward