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


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

CLI-based Configuration Guide - Reliability
AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009
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


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

After EFM connections have been established, both EFM entities exchange Information OAMPDUs. When traffic is interrupted because an EFM entity fails or becomes unavailable, the faulty EFM entity will send an Information OAMPDU carrying a critical link event flag to its remote EFM entity, record a log, and send an alarm. This mechanism helps administrators to learn the link status in real time and troubleshoot link faults promptly.

As shown in Figure 8-8, if a fault occurs on PE2, PE2 sends an Information OAMPDU carrying 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-8  Remote fault indication and association between EFM and an interface

Pre-configuration Tasks

Before configuring remote fault indication, complete the following task:


  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. 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 on the interface are interrupted. 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.

Updated: 2019-05-17

Document ID: EDOC1000174116

Views: 67794

Downloads: 26

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next