Creating an ME Instance and Binding It to a PW

This section describes how to create an ME instance and bind it to a PW.

Context

To use Multiprotocol Label Switching Transport Profile (MPLS-TP) operation, administration and maintenance (OAM) to monitor a PW, you must create an ME instance and bind it to the PW.

Procedure

Run system-view
The system view is displayed.
Run mpls-tp mode { standard | private }
A detection mode is configured for MPLS-TP OAM.
(Optional) Run mpls-tp channel-type {0x7ffa | 0x8902 }
An ACH label value is specified.
Run mpls-tp meg meg-name
A MEG is created, and the MEG view is displayed.
Create an ME instance and bind it to a single- or multi-segment PW.
- If the PW is a single-segment PW, the configuration steps are as follows:
  - On the local MEP, run me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type mep-id mep-id remote-mep-id remote-mep-id
    An ME instance is created and bound to a single-segment PWE3 PW.
  - On the RMEP, run me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type mep-id mep-id remote-mep-id remote-mep-id
    An ME instance is created and bound to the same single-segment PWE3 PW.
- If the PW is a multi-segment PW, the ttl parameter must be specified:
  - On the local MEP, run me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type [ remote-peer-ip remote-peer-ip | ttl ttl-number ] mep-id mep-id remote-mep-id remote-mep-id [ gal { 13 | 14 } ]
    An ME instance is created and bound to a multi-segment PWE3 PW.
  - On the RMEP, run me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type [ remote-peer-ip remote-peer-ip | ttl ttl-number ] mep-id mep-id remote-mep-id remote-mep-id [ gal { 13 | 14 } ]
    An ME instance is created and bound to the same multi-segment PWE3 PW.
Run commit
The configuration is committed.