No relevant resource is found in the selected language.
MENU
Support Documentation
NE20E-S V800R012C00SPC300 Configuration Guide - Network Reliability 04
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring MPLS-TP OAM for a PW

Configuring MPLS-TP OAM for a PW

This section describes how to configure Multiprotocol Label Switching Transport Profile (MPLS-TP) operation, administration and maintenance (OAM) for a pseudo wire (PW). The NE20E can monitor PWs using MPLS-TP OAM.

Usage Scenario

MPLS-TP has been widely used on transport networks. Since traditional transport networks (such as SDH and OTN networks) set high benchmarks for reliability and maintenance, MPLS-TP must provide powerful OAM capabilities.

MPLS-TP OAM can detect faults in a PW and collect performance statistics. On the PW shown in Figure 11-4, T-PEs are the maintenance entity group end points (MEPs), and S-PEs are the maintenance entity group intermediate points (MIPs). MPLS-TP OAM runs on the MEPs and provides connectivity check, frame loss measurement, and frame delay measurement.

Figure 11-4 PW over a bidirectional LSP

Table 11-6 describes the support of MPLS-TP OAM detection for different types of PWs.

Table 11-6 Support of MPLS-TP OAM detection for different types of PWs

Function

Static VPWS

Static VPLS

CC/CV

Support

Support

LB

Support

Not support

LM

Support

Not support

DM

Support

Not support

Pre-configuration Tasks

Before configuring MPLS-TP OAM for a PW, complete the following tasks:

  • Configure a PW over a bidirectional LSP.

  • Enable performance statistics collection for the attachment circuit (AC) interface of the PW.

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

  1. Run system-view

    The system view is displayed.

  2. Run mpls-tp mode { standard | private }

    A detection mode is configured for MPLS-TP OAM.

  3. (Optional) Run mpls-tp channel-type {0x7ffa | 0x8902 }

    An ACH label value is specified.

  4. Run mpls-tp meg meg-name

    A MEG is created, and the MEG view is displayed.

  5. 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.

  6. Run commit

    The configuration is committed.

(Optional) Configuring CC and CV for an LSPa TE-LSP

This section describes how to configure continuity check (CC) and connectivity verification (CV) for an LSP.

Context

CC and CV are two fault management functions of Multiprotocol Label Switching Transport Profile (MPLS-TP) operation, administration and maintenance (OAM). CC is used to detect loss of continuity (LOC) between maintenance entity group end points (MEPs) in a maintenance entity group (MEG). CV is used to detect forwarding errors between MEGs or between MEPs in a MEG. CC and CV are both proactive OAM operations but have the following differences:

  • CC detects LOC on a link between any MEPs in a MEG. A MEP sends continuity check messages (CCMs) to its remote MEP (RMEP) at a specified interval. If the RMEP does not receive CCMs within a period of 3.5 times as long as the specified interval, the RMEP considers that the connectivity between the MEPs has errors, reports an alarm, and enters the Down state. After that, automatic protection switching (APS) is triggered on both MEPs. Upon receipt of a CCM from the MEP, the RMEP clears the alarm and exits from the Down state.

  • CV enables a MEP to report alarms when receiving unexpected packets. For example, if a CV-enabled device receives a packet from an LSP and finds that this packet is incorrectly transmitted through the LSP, the device will report an alarm indicating a forwarding error.

    Transport networks have strict requirements on the correctness of data forwarding. In addition, MPLS-TP requires that the data plane should be able to work without IP support, which means that packet forwarding is based on label switching only. Therefore, the correctness of label-based forwarding must be ensured.

In practice, CC and CV are used together in the NE20E. The configurations for CC and CV are the same. Perform the following steps on a MEP and its RMEP:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls-tp meg meg-name

    A MEG is created, and the MEG view is displayed.

  3. (Optional) Run either of the following commands:

    Ensure that the same value is set on the MEP and RMEP; otherwise, an alarm will be generated.

    • To configure an interval at which CCMs are sent, run the cc interval interval-value command.

      Optional CCM transmission intervals and their usage scenarios are as follows:
      • 3.3 ms: 300 frames are sent per second. This interval is recommended for protection switching.
      • 10 ms: 100 frames are sent per second.
      • 100 ms: 10 frames are sent per second. This interval is recommended for performance monitoring.
      • 1000 ms: 1 frame is sent per second. This interval is recommended for fault management.
      • 10000 ms: 6 frames are sent per minute.
      • 60000 ms: 1 frame is sent per minute.
      • 600000 ms: 6 frames are sent per hour.
      Select a proper CCM transmission interval to meet CC application requirements.

    • To configure a priority for CCMs, run the cc exp exp-value command.

      If the MPLS-TP network is severely congested and the priority of CCMs is low, CCMs fail to be sent. Therefore, configure an appropriate priority for CCMs according to network conditions.

  4. (Optional) On the local MEP, run rdi disable

    RDI is disabled.

    RDI is enabled by default.

    If an MEP detects a defect or fault, the RDI flag is set to 1 in CCMs. The MEP then sends the CCMs to the RMEP to notify it of the defect or fault.

  5. Perform the following steps to enable CC and CV on the MEP and RMEP (this operation sequence prevents alarm misreports during the enabling process):
    1. Run the cc send enable command on the MEP to enable the MEP to send CCMs.
    2. Run the cc send enable command on the RMEP to enable the RMEP to send CCMs.
    3. Run the cc receive enable command on the MEP to enable the MEP to receive CCMs.
    4. Run the cc receive enable command on the RMEP to enable the RMEP to receive CCMs.

(Optional) Configuring LB for an LSP

This section describes how to configure loopback (LB) to monitor the connectivity of MPLS-TP links.

Context

LB is the most common tool that monitors the connectivity between MEPs or between a MEP and a MIP. Unlike CC or CV that is performed periodically, LB is performed at a time.

Commands can be run to trigger LB, and LB packets are used to check the following information:
  • Availability of a remote device
  • Round-trip delay in communication between MEPs
  • Loss of ping packets
Both the loopback function enabled using the ping meg command and CC enabled using the cc enable command are used to monitor the connectivity of bidirectional links. The following table describes differences between them.
Table 11-7 Differences between loopback and CC

Item

Loopback enabled using the ping meg command

CC enabled using the cc enable command

Configuration procedure

To enable loopback, perform the following step:

Run the ping meg command on a MEP to enable loopback and display statistics in real time.
To enable CC, perform the following steps:
  1. (Optional) Run the cc interval command to set an interval at which CCMs are sent on a MEP and its RMEP.
  2. (Optional) Run the cc exp command to set a priority for CCMs on the MEP and its RMEP.
  3. Run the cc send enable command to enable the MEP and its RMEP to send CCMs.
  4. Run the cc receive enable command to enable the MEP and its RMEP to receive CCMs.

Statistics display

The ping meg command displays statistics on the MEP.

An alarm is generated and reported if a connectivity fault between the MEP and its RMEP occurs.

Detection method

On-demand monitoring: monitors connectivity of a MEG at a time.

Proactive monitoring: periodically monitors connectivity of a MEG.

Detection object

MEP or MIP

MEP

Procedure

  • Run ping meg meg-name [ { mip ttl ttl-number { mip-id mip-id-value | node-id node-id value } [ if-num if-numvalue ] } | -c count-value | packet-size size-value | -t timeout-value ] * [ request-tlv ]

    LB is enabled to monitor the connectivity of an MPLS-TP link.

    The timeout-value parameter specifies a period for waiting for a response packet.

    If the network speed is slow, set the timeout-value parameter to a large value in the ping meg command.

(Optional) Configuring Frame LM

This section describes how to configure frame loss measurement (LM) for MPLS-TP services.

Context

Frame LM is a performance monitoring function provided by MPLS-TP OAM. Dual-ended frame LM is performed on the two MEPs of a service link. Measurement results include the following data:
  • Near-end frame loss data: indicates the number and percentage of lost frames that are sent from an RMEP to a MEP.
  • Far-end frame loss: indicates the number and percentage of dropped frames that are sent from a MEP to an RMEP.
The NE20E supports single-ended frame LM and dual-ended frame LM. The following table describes their differences.
Table 11-8 Differences between single-ended frame LM and dual-ended frame LM

Item

Single-ended Frame LM

Dual-ended Frame LM

Statistics display
Statistics can be displayed using either of the following commands on a MEP:
  • To display statistics about single-ended on-demand frame LM, run the lost-measure single-ended command.
  • To display statistics about single-ended frame LM, run the display mpls-tp oam meg meg-name statistic-type lost-measure single-ended command.

Statistics about dual-ended frame LM can be displayed using the display mpls-tp oam meg meg-name statistic-type lost-measure dual-ended command on a MEP.

Monitoring scenario

On-demand monitoring

Proactive monitoring

Proactive monitoring
The procedure for configuring single-ended or dual-ended frame LM is as follows:

All the steps must be performed on both the MEP and RMEP unless otherwise specified.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls-tp meg meg-name

    A MEG is created, and the MEG view is displayed.

  3. Choose one of the following sub-procedures as needed:

    • Configure single-ended frame LM.
      1. Run lost-measure single-ended receive enable

        The RMEP is enabled to receive LMMs from the MEP.

      2. Perform either of the following steps:

        • Run lost-measure single-ended [ count count-value | exp exp-value | interval interval-value ]*

          Single-ended on-demand frame LM is enabled on the MEP.

        • Run lost-measure single-ended proactive [ interval interval-value | exp exp-value ] *

          Single-ended proactive frame LM is enabled on the MEP.

    • Configure dual-ended frame LM.

      1. (Optional) Run cc interval interval-value

        An interval at which CCMs are sent is configured.

        Typical CCM transmission intervals and their application scenarios are as follows:
        • 3.3 ms: 300 frames are sent per second. This interval is recommended for protection switching.
        • 100 ms: 10 frames are sent per second. This interval is recommended for performance monitoring.
        • 1000 ms: 1 frame is sent per second. This interval is recommended for fault management.

      2. (Optional) Run cc exp exp-value

        A priority is configured for CCMs.

        If the MPLS-TP network is severely congested and the priority of CCMs is low, CCMs fail to be sent. Therefore, configure an appropriate priority for CCMs according to network conditions.

      3. On the MEP, run cc send enable

        The MEP is enabled to send CCMs.

      4. On the RMEP, run cc send enable

        The RMEP is enabled to send CCMs.

      5. On the MEP, run cc receive enable

        The MEP is enabled to receive CCMs.

      6. On the RMEP, run cc receive enable

        The RMEP is enabled to receive CCMs.

      7. Run lost-measure dual-ended enable

        Dual-ended frame LM is enabled.

(Optional) Configuring Frame DM

This section describes how to configure one- and two-way frame delay measurement (DM) to collect reliability statistics for MPLS-TP services.

Context

Frame DM, a performance monitoring function provided by MPLS-TP, calculates the delay on links. The delay can be used to calculate the delay variation. The following DM modes are supported:
  • One-way frame DM: In a point-to-point ME, a MEP sends DM frames to its RMEP to carry out one-way frame delay and variation measurement.

    If the clocks of the two MEPs are synchronized, one-way frame DM can be conducted; otherwise, only two-way frame delay variation can be measured.

  • Two-way frame DM: In a point-to-point ME, a MEP sends delay measurement messages (DMMs) to its RMEP and receives delay measurement replies (DMRs) from the RMEP to carry out two-way frame delay and variation measurement.
One-way frame DM and two-way frame DM have the same monitoring scenario. The following table describes differences between them.
Table 11-9 Differences between one-way frame DM and two-way frame DM

Item

One-Way Frame DM

Two-Way Frame DM

Statistics display

Statistics about one-way frame DM can be displayed using the display mpls-tp oam meg meg-name statistic-type delay-measure one-way command on an RMEP.
Statistics can be displayed using either of the following commands on a MEP:

  • To display statistics about two-way on-demand frame DM, run the delay-measure two-way [ interval interval-value | count count-value | exp exp-value | two-time-stamp ]* command.

  • To display statistics about two-way frame DM, run the display mpls-tp oam meg meg-name statistic-type delay-measure two-way command.

Monitoring scenario

On-demand monitoring

Proactive monitoring

On-demand monitoring

Proactive monitoring
The procedure for configuring one-way or two-way frame DM is as follows:

All the steps must be performed on both the MEP and RMEP unless otherwise specified.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls-tp meg meg-name

    A MEG is created, and the MEG view is displayed.

  3. Choose one of the following sub-procedures as needed:

    • Configure one-way frame DM. Run any of the following commands:

      • Run delay-measure one-way [ interval interval-value | count count-value | exp exp-value ] *

        One-way on-demand frame DM is enabled.

        Run either of the following commands to view statistics about one-way on-demand frame DM as needed:

        • If the delay-measure one-way command has been run on the MEP to measure the delay on the link from the MEP to the RMEP, run the display mpls-tp oam meg meg-name statistic-type delay-measure one-way command on the RMEP to view DM results.
        • If the delay-measure one-way command has been run on the RMEP to measure the delay on the link from the RMEP to the MEP, run the display mpls-tp oam meg meg-name statistic-type delay-measure one-way command on the MEP to view DM results.

      • On the MEP, run delay-measure one-way proactive [ interval interval-value | exp exp-value ] *

        One-way proactive frame DM is enabled.

        On the RMEP, run delay-measure one-way proactive receive enable

        The receive function is enabled for one-way proactive frame DM.

        Run either of the following commands to view statistics about one-way proactive frame DM as needed:

        • If the delay-measure one-way proactive command has been run on the MEP, run the display mpls-tp oam meg meg-name statistic-type delay-measure one-way command on the RMEP to view statistics about one-way proactive frame DM in the direction from the MEP to its RMEP.
        • If the delay-measure one-way proactive command has been run on the RMEP, run the display mpls-tp oam meg meg-name statistic-type delay-measure one-way command on the MEP to view statistics about one-way proactive frame DM in the direction from the RMEP to its MEP.

    • Configure two-way frame DM. Configure either two-way on-demand or proactive frame DM as follows:

      • To enable two-way on-demand frame DM, run the delay-measure two-way [ interval {1000|10000} | count count-value | exp exp-value | two-time-stamp ] * command.

      • To enable two-way proactive frame DM, run the delay-measure two-way proactive [ interval { 1000 | 10000 } | exp exp-value ] * command.

Verifying the Configuration of MPLS-TP OAM for a PW

After configuring Multiprotocol Label Switching Transport Profile (MPLS-TP) operation, administration and maintenance (OAM) for a pseudo wire (PW), verify the configurations by querying performance statistics and fault detection information.

Prerequisites

MPLS-TP OAM has been configured for a PW.

Procedure

  • Run the display mpls-tp oam current-alarm command to check alarms associated with a MEG.
  • Run the display mpls-tp oam me brief command to check information about maintenance entities (MEs) in a MEG.
  • Run the display mpls-tp oam meg command to check MEG information on the MEP.
  • Run the display mpls-tp oam meg meg-name statistic-type command to check MPLS-TP OAM performance statistics.
Translation
简体中文
Download
Updated: 2020-07-02

Document ID: EDOC1100146989

Views: 6292

Downloads: 3

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next
Enterprise APP

Copyright © 2021 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :