No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - Reliability

S2720, S5700, and S6720 V200R013C00

This document describes the configurations of Reliability, including BFD Configuration, VRRP Configuration, DLDP Configuration, Smart Link and Monitor Link Configuration, MAC Swap Loopback Configuration, EFM Configuration, CFM Configuration, Y.1731 Configuration.

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).
Understanding Y.1731

Understanding Y.1731

Function Overview

Y.1731 can manage fault information and monitor performance.
  • Fault management functions include continuity check (CC), loopback (LB), and linktrace (LT). Y.1731 fault management is similar to CFM fault management.

  • Performance monitoring functions include single-ended synthetic loss measurement, one- and two-way frame delay measurement and alarm indication signal (AIS) on virtual local area networks (VLANs).

    NOTE:

    Only the S5720EI, S5720HI, S5720I-SI, S5720S-SI, S5720SI, S5730HI, S5730S-EI, S5730SI, S6720EI, S6720HI, S6720LI, S6720S-EI, S6720S-LI, S6720S-SI, and S6720SI support AIS.

Table 9-1  Y.1731 functions

Function

Purpose

Usage

One-way Frame Delay Measurement

Measures the network delay time on a unidirectional link between MEPs.

  • One-way frame delay measurement is used to measure the delay time on a unidirectional link between a MEP and its RMEP. The MEP must synchronize its time with its RMEP.

  • Two-way frame delay measurement is used to measure the delay time on a bidirectional link between a MEP and its RMEP. The MEP does not need to synchronize its time with its RMEP.

Two-way Frame Delay Measurement

Measures the network delay time on a bidirectional link between MEPs.

Single-ended Synthetic Loss Measurement

Collects frame loss statistics on point-to-multipoint links to monitor link quality.

Single-ended synthetic frame LM is used to collect accurate frame loss statistics on point-to-multipoint links.

AIS

Detects server-layer faults and suppresses alarms, minimizing the impact on network management systems (NMSs).

AIS is used to suppresses local alarms in the scenario where faults must be rapidly detected. When CFM detects connectivity faults, AIS suppresses generated alarms.

Multicast MAC Ping

Identifies faults and discovers RMEPs.

  • Multicast MAC ping is used to detect faults in links between MEPs in the scenario where multiple MEPs are used.

  • Multicast MAC ping is used to discover RMEPs if RMEP IDs and MAC addresses cannot be obtained.

ETH-DM

Delay measurement (DM) measures the delay time and delay variation. A MEP sends a message carrying ETH-DM information to its RMEP and then receives a response message carrying ETH-DM information from its RMEP.

ETH-DM supports the following methods:
  • One-way frame delay measurement

    A MEP sends a 1DM message carrying one-way ETH-DM information to its RMEP. After receiving this message, the RMEP measures the one-way frame delay or delay variation.

    One-way frame delay measurement can be implemented only after the MEP synchronizes the time with its RMEP. The delay variation can be measured regardless of whether the MEP synchronizes the time with its RMEP. If a MEP synchronizes its time with its RMEP, the one-way frame delay and delay variation can be measured. If the time is not synchronized, only the one-way delay variation can be measured.

    One-way frame delay measurement can be implemented in either of the following modes:
    • On-demand measurement calculates the one-way frame delay at a time or a specific number of times for diagnosis.

    • Proactive measurement calculates the one-way frame delay periodically.

    In on-demand or proactive mode, a MEP sends 1DM frames to its RMEP. Figure 9-2 illustrates the procedure for one-way delay measurement.

    Figure 9-2  One-way frame delay measurement

    One-way frame delay measurement is implemented on an end-to-end link between a local MEP and its RMEP by exchanging 1DM frames. After one-way frame delay measurement is configured, a MEP periodically sends 1DM frames carrying TxTimeStampf (the time when the 1DM frame was sent). After receiving a 1DM frame, the RMEP parses TxTimeStampf and compares this value with RxTimef (the time when the 1DM frame was received). The RMEP calculates the one-way frame delay based on these values using the following formula:

    Frame delay = RxTimef – TxTimeStampf

    The frame delay value can be used to measure the delay variation.

    A delay variation is an absolute difference between two delays.

    Service packets are prioritized based on 802.1p priorities and are transmitted using different policies. Traffic passing through a P on the network shown in Figure 9-3 carries 802.1p priority values of 1 and 2.

    One-way delay measurement is enabled on PE1 to send traffic with the priority value of 1 to measure the frame delay on a link between PE1 and PE2. Traffic with the priority value of 2 is also sent. After receiving traffic with the priority values of 1 and 2, the P forwards traffic with a higher priority, delaying the arrival of traffic with the priority value of 1 at PE2. As a result, the frame delay calculated on PE2 is inaccurate.

    802.1p priority-based one-way frame delay measurement can be enabled to obtain accurate results.

    Figure 9-3  802.1p priority-based one-way frame delay measurement
  • Two-way frame delay measurement

    A MEP sends a delay measurement message (DMM) carrying an ETH-DM request to its RMEP. After receiving the DMM, the RMEP sends a delay measurement reply (DMR) carrying an ETH-DM response to the MEP.

    Two-way frame delay measurement can be implemented in either of the following modes:
    • The on-demand measurement calculates the two-way frame delay at a time for diagnosis.

    • The proactive measurement calculates the two-way frame delay periodically.

    Figure 9-4 illustrates the procedure for two-way delay measurement.

    Figure 9-4  Two-way frame delay measurement

    Two-way frame delay measurement is performed by a local MEP to send a DMM to its RMEP and then receive a DMR from the RMEP. After the two-way frame delay measurement is configured, a MEP periodically sends DMMs carrying TxTimeStampf (the time when the DMM was sent). After receiving the DMM, the RMEP replies with a DMR. The DMR carries RxTimeStampf (the time when the DMM was received) and TxTimeStampb (the time when the DMR was sent). The value in every field of the DMM is copied to the DMR except that the source and destination MAC addresses were interchanged. Upon receiving the DMR, the MEP calculates the two-way frame delay by using the following formula:

    Frame delay = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)

    The frame delay value can be used to measure the delay variation.

    A delay variation is an absolute difference between two delays.

    Service packets are prioritized based on 802.1p priorities and are transmitted using different policies. Traffic passing through a P on the network shown in Figure 9-5 carries 802.1p priority values of 1 and 2.

    Two-way delay measurement is enabled on PE1 to send traffic with the priority value of 1 to measure the frame delay on a link between PE1 and PE2. Traffic with the priority value of 2 is also sent. After receiving traffic with the priority values of 1 and 2, the P forwards traffic with a higher priority, delaying the arrival of traffic with the priority value of 1 at PE2. As a result, the frame delay calculated on PE2 is inaccurate.

    802.1p priority-based two-way frame delay measurement can be enabled to obtain accurate results.

    Figure 9-5  802.1p priority-based two-way frame delay measurement

Single-ended synthetic loss measurement (SLM)

SLM measures frame loss using synthetic frames instead of data traffic. When implementing SLM, the local MEP exchanges frames containing ETH-SLM information with one or more RMEPs.

Figure 9-6 demonstrates the process of single-ended SLM:
  1. The local MEP sends frames with the ETH-SLM request information to the RMEPs.

  2. After receiving the frames with the ETH-SLM request information, the RMEPs send frames with the ETH-SLM reply information to the local MEP.

A frame with the single-ended ETH-SLM request information is called an SLM, and a frame with the single-ended ETH-SLM reply information is called an SLR. SLM frames carry SLM protocol data units (PDUs), and SLR frames carry SLR PDUs.
Figure 9-6  Networking diagram for single-ended SLM

AIS

Alarm indication signal (AIS) is used to transmit fault information.

A MEP is configured in MD1 with the level of 6 on each of customer edge CE1 and CE2 access interfaces on the user network shown in Figure 9-7. A MEP is configured in MD2 with the level of 3 on each of PE1 and PE2 access interfaces on a carrier network.
  • If CFM detects a fault in the link between AIS-enabled PEs, CFM sends AIS packet data units (PDUs) to CEs. After receiving the AIS PDUs, the CEs suppress alarms, minimizing the impact of a lot of alarms on a network management system (NMS).

  • After the link between the PEs recovers, the PEs stop sending AIS PDUs. CEs do not receive AIS PDUs during a period of time 3.5 times as long as the interval at which AIS PDUs are sent. Therefore, the CEs cancel the alarm suppression function.

Figure 9-7  AIS implementation

Multicast MAC Ping

The destination MAC address of a multicast MAC ping packet is a multicast MAC address. Multicast MAC ping provides the following functions:
  • Fault verification

    Fault verification provided by multicast MAC ping is similar to that provided by 802.1ag MAC ping. They are both used to check the reachability between the local and destination devices by sending test packets. Unlike 802.1ag MAC ping, multicast MAC ping can detect faults in links between multiple MEPs at a time.

    Multicast MAC ping is applied to the networking where multiple MEPs are deployed. Multicast MAC ping is initiated by the local MEP and responded to by the remote MEP.

    Figure 9-8  Networking diagram for multicast MAC ping
    As shown in Figure 9-8, MEP1 on PE1 has two remote MEPs, namely, MEP2 and MEP3. MEP1 initiates a multicast MAC ping probe. The probe process is as follows:
    • In the case where the link between MEP1 and MEP2 or between MEP1 and MEP3 is normal:

      1. MEP1 of the local device sends a multicast LBM.

      2. After receiving the multicast LBM, MEP2 and MEP3 reply with an LBR.

      3. The local device receives the LBRs and displays the contents of the LBRs.

    • In the case where the link between MEP1 and MEP2 or between MEP1 and MEP3 is faulty:
      1. MEP1 of the local device sends a multicast LBM.

      2. MEP1 does not receive any LBR from the remote MEPs within a specified timeout period. The output of the related command shows that a fault occurs on the link between MEP1 and MEP2 or the link between MEP1 and MEP3.

  • Remote MEP discovery

    As shown in Figure 9-8, remote MEPs need to be configured for MEP1 of PE1. The IDs and MAC addresses of the remote MEPs may be unknown. Therefore, multicast MAC ping can be performed to discover the remote MEPs of MEP1. The process of multicast MAC ping is as follows:
    1. MEP1 of the local device sends a multicast LBM.

    2. After receiving the multicast LBM, MEP2 and MEP3 reply with an LBR.

    3. The local device receives the LBRs and displays the contents of the LBRs. The LBRs contain the MAC addresses of the remote MEPs, MEP IDs, and delay.

Usage Scenario

Y.1731 applies to virtual local area networks (VLANs). AIS is the same in these scenarios. Different Y.1731 statistical functions are supported in specific scenarios. The following example illustrates Y.1731 statistical functions in different scenarios on the network shown in Figure 9-9.

Figure 9-9  Y.1731 statistical functions in specific scenarios
A VLAN is configured between a CE and PE1 on the network. Y.1731 can be used on the link between the CE and PE1. Figure 9-10 lists supported Y.1731 statistical functions.
Figure 9-10  Y.1731 statistical functions in the VLAN scenario
Translation
Download
Updated: 2019-04-04

Document ID: EDOC1100065682

Views: 35799

Downloads: 257

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next