me te interface

Function

The me te interface command creates an ME instance and binds it to a bidirectional TE tunnel.

The undo me te interface command deletes an ME instance bound to a bidirectional TE tunnel.

By default, no ME instance is created.

Format

me te interface { interface-type interface-number | interface-name } mep-id mep-id remote-mep-id remote-mep-id

undo me te interface { interface-type interface-number | interface-name }

Parameters

Parameter Description Value
interface-type

Specifies the type of an interface.

-

interface-number

Specifies the number of an interface.

-

mep-id mep-id

Specifies the local MEP ID. A MEP ID identifies a MEP. The MEP ID must be unique in an ME.

The value is an integer ranging from 1 to 8191.

remote-mep-id remote-mep-id

Specifies the remote MEP (RMEP) ID. A MEP ID identifies a MEP. The MEP ID must be unique in an ME.

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

Two P2P label switched paths (LSPs) in opposite directions are established over a bidirectional co-routed transport path in a MEG. This means that there is a single LSP in both directions between a MEP and its RMEP. A single ME operates along this P2P LSP. The ingress and egress of a bidirectional co-routed LSP function as the MEPs.

The me te interface command is run to perform OAM detection on a bidirectional co-routed P2P LSP. The configuration procedure is as follows:

  • Run the me te interface mep-id remote-mep-id command on the local MEP to create an ME instance and bind it to a bidirectional co-routed P2P LSP.
  • Run the me te interface mep-id remote-mep-id command on the RMEP to create an ME instance and bind it to the same bidirectional co-routed P2P LSP.

Prerequisites

A static bidirectional co-routed P2P LSP has been established.

Precautions

MPLS-TP OAM does not support LDP over TE.

If MPLS-TP OAM is already associated with an APS tunnel protection group, an ME instance bound to a bidirectional co-routed TE tunnel cannot be deleted.

Example

# Create an ME instance in a MEG named abc and bind it to a bidirectional co-routed P2P LSP.
<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] quit
[*HUAWEI] interface tunnel 10
[*HUAWEI-Tunnel10] tunnel-protocol mpls te
[*HUAWEI-Tunnel10] mpls te signal-protocol cr-static
[*HUAWEI-Tunnel10] mpls te bidirectional
[*HUAWEI-Tunnel10] quit
[*HUAWEI] mpls-tp meg abc
[*HUAWEI-mpls-tp-meg-abc] me te interface Tunnel 10 mep-id 1 remote-mep-id 2
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >