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

S9300, S9300E, and S9300X V200R011C10

This document describes the configuration of BFD, DLDP, VRRP, SmartLink, CFM, EFM, Y.1731 and MAC swap loopback to ensure reliability on the device.
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 Remote Fault Indication

Configuring Remote Fault Indication

Context

Remote fault indication is used to detect remote device faults and monitor Ethernet performance.

Remote fault indication is used to detect remote device faults and monitor Ethernet performance. After EFM connections have been established, EFM entities exchange Information OAMPDUs. When traffic is interrupted because an EFM entity fails or becomes unavailable, the faulty EFM entity sends an Information OAMPDU that carries a critical link event flag to its remote EFM entity, record a log, and send an alarm. The remote fault indication helps administrators to learn the link status in real time and troubleshoot link faults promptly.

In Figure 8-13, if a fault occurs on PE2, PE2 sends an Information OAMPDU that carries a critical link event flag to the CE. Association between EFM and Port1 is triggered and services are switched to the backup path. This association ensures reliable traffic transmission.

Figure 8-13  Remote fault indication and association between EFM and an interface

EFM can be configured on Layer 2 and Layer 3 Ethernet interfaces. By default, an Ethernet interface works in Layer 2 mode. Before configuring EFM on a Layer 3 Ethernet interface, switch the Ethernet interface to Layer 3 mode.

Pre-configuration Tasks

Before configuring remote fault indication, perform the task of Configuring Basic EFM Functions.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The view of the interface at one end of the link is displayed.

  3. (Optional) On an Ethernet interface, run undo portswitch

    The interface is switched to Layer 3 mode.

    By default, an Ethernet interface works in Layer 2 mode.

  4. Run efm { critical-event | dying-gasp | link-fault | timeout } trigger error-down

    Association between EFM and the interface is configured. The association will be triggered if a remote fault occurs.

    By default, association between EFM and the interface is not triggered by a remote fault.

    The efm trigger error-down command associates an error event with an interface. When EFM detects critical-event, dying-gasp, link-fault, or timeout faults, the protocol status of the interface becomes Down and all services are interrupted on the interface. Traffic will not be switched back even if the faulty link recovers and the protocol status of the interface does not change. You need to manually check link quality before switching traffic back to the original link.

Translation
Download
Updated: 2019-04-17

Document ID: EDOC1000178423

Views: 91511

Downloads: 25

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next