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

CLI-based Configuration Guide - Reliability

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides guidance for configuring reliability services, including interface backup, BFD, VRRP, and EFM.
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).
Fault Information Advertisement Between EFM and Other Modules

Fault Information Advertisement Between EFM and Other Modules

Fault Information Advertisement Between EFM and Detection Modules

The OAMMGR module associates EFM with detection modules. The detection modules can be bidirectional forwarding detection (BFD) and interface. Figure 8-6 shows the network on which fault information is advertised between EFM and detection modules.

Figure 8-6  Fault information advertisement between EFM and detection modules

The following example illustrates fault information advertisement between EFM and detection modules over the path CE5 -> CE4 -> CE1 -> PE2 -> PE4, as described in Table 8-6.

Table 8-6  Fault information advertisement between EFM and detection modules

Function Deployment

Issue to Be Resolved

Solution

EFM is configured to monitor a direct link between CE1 and CE4.

Although EFM detects a fault on a direct link between CE1 and CE4, PE2 cannot detect this fault. As a result, network-side traffic is still sent to CE4, causing a traffic interruption.

Although Port1 on CE1 goes Down, Port1 cannot notify CE4 of the fault. As a result, CE4 still forwards user traffic to CE1, causing a traffic interruption.

EFM and Port1 are associated with each other. If a fault occurs, traffic switches to a standby link between CE1 and CE5.
  • If EFM detects a fault on a direct link between CE1 and CE4, EFM instructs the OAMMGR module to notify Port1 of the fault. After receiving the notification, Port1 changes its physical status to TRIGGER DOWN (3AH).

  • If Port1 goes Down, it instructs the OAMMGR module to notify the EFM module of the fault. After receiving the notification, EFM notifies CE4 of the fault.

EFM is used to monitor a direct link between CE1 and PE2, and BFD is used to monitor a link between PE2 and PE6.

  • Although EFM detects a fault, EFM cannot notify PE6 of the fault. As a result, traffic is still sent to PE6, causing a traffic interruption.

  • Although BFD detects a fault, EFM cannot notify CE1 of the fault. As a result, CE1 still forwards user traffic to PE2, causing a traffic interruption.

The EFM module can be associated with the BFD module.
  • If the EFM module detects a fault, it instructs an OAMMGR module to notify the BFD module of the fault.

  • If the BFD module detects a fault, it instructs the OAMMGR module to notify the EFM module of the fault.

The association allows a module to notify another associated module of a fault and send a trap to the NMS. A network administrator analyzes alarm information and takes measures to rectify the fault.
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100069338

Views: 14059

Downloads: 40

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