me mip switch-l2vc between vc-type

Function

The me mip switch-l2vc between vc-type command creates a maintenance entity (ME) instance for a maintenance entity group intermediate point (MIP) and binds the ME instance to a switch node over a multi-segment PW (MS-PW).

The undo me mip switch-l2vc between vc-type command deletes an ME instance created on a MIP.

By default, no ME instance is created.

Format

me mip switch-l2vc peer-ip-value vc-id-value between switch-peer-ip-v switch-vc-id-v vc-type vc-type-value [ mip-id mip-id-value ]

undo me mip switch-l2vc peer-ip-value vc-id-value between switch-peer-ip-v switch-vc-id-v vc-type vc-type-value

Parameters

Parameter	Description	Value
peer-ip-value	Specifies the label switching router (LSR) ID for the PE over an MS-PW.	The value is in dotted decimal notation.
vc-id-value	Specifies the virtual circuit (VC) ID.	The value is an integer ranging from 1 to 4294967295. VCs of the same type on a PE must be uniquely identified by the VC ID.
switch-peer-ip-v	Specifies the LSR ID for the peer PE of the switch node over an MS-PW.	The value is in dotted decimal notation.
switch-vc-id-v	Specifies the VC ID.	The value is an integer ranging from 1 to 4294967295. VCs of the same type on a PE must be uniquely identified by the VC ID.
vc-type-value	Specifies the VC type.	Encapsulation types supported: Other encapsulation types: cep: This encapsulation type is used for CEP services. ethernet: This encapsulation type is used when Ethernet packets do not carry VLAN information. ip-interworking: This encapsulation type is used for interworking between Huawei devices. ip-layer2: This encapsulation type is used for interworking between Huawei devices and non-Huawei devices. vlan: This encapsulation type is used when Ethernet packets carry VLAN information.
mip-id mip-id-value	Specifies the ID of a MIP.	The value is an integer ranging from 1 to 8191.

Views

Maintenance entity group view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
tpoam	write

Usage Guidelines

Usage Scenario

If an MS-PW is used as a transport path, a MEG must have a single ME for this MS-PW. The MIP is the switch node over the MS-PW.

To monitor the path between the MEP and the MIP using MPLS-TP OAM, create ME instances on both the MEP and MIP. To create an ME instance on the MIP and bind the ME instance to the switch node over the MS-PW, run the me mip switch-l2vc command.

MPLS-TP OAM supports only the loopback (LB) function to monitor a path from a MEP to a MIP. If a MEP sends a loopback message (LBM), a destination node MIP can be specified. After receiving the LBM, the MIP responds to the MEP with a loopback reply (LBR). This process completes the LB operation.

Prerequisites

A switch node exists on the MS-PW.

Configuration Impact

After the me mip switch-l2vc command is run:

The MIP responds to the MEP with LBRs and does not initiate the LB detection.
The MIP does not detect the MEG ID on the MEP side and cannot verify the MEG ID.
The MIP does not support performance statistics.

Example

# Create an ME instance on the MIP and binds the ME instance to the switch node.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] mpls l2vpn
[*HUAWEI-l2vpn] quit
[*HUAWEI] mpls switch-l2vc 1.1.1.1 100 between 3.3.3.3 100 encapsulation vlan
[*HUAWEI] mpls-tp meg test
[*HUAWEI-mpls-tp-meg-test] me mip switch-l2vc 1.1.1.1 100 between 3.3.3.3 100 vc-type vlan