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. On an LSP, a maintenance entity group end point (MEP) is configured on the ingress and a remote MEP (RMEP) is configured on the egress. A MIP is configured on the transit node.
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 it to a specified LSP, run the
me mip te 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 transit node exists on a static bidirectional co-routed LSP.
Configuration Impact
After the me mip te bidirectional-lsp command is run:
- The MIP responds to the MEP with LBRs and does not initiate the LB detection.
- The MIP does not support performance statistics.
- The MIP does not detect the MEG ID on the MEP side and cannot verify the MEG ID.