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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Reliability, including BFD Configuration, VRRP Configuration, DLDP Configuration, Smart Link and Monitor Link Configuration, EFM Configuration, and CFM 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).
CFM Association

CFM Association

Association Between CFM and Detection Modules

The OAMMGR module can associate CFM with detection modules. The detection modules can be EFM, BFD, CFM, and interface. Figure 7-14 shows the network on which fault information is advertised between CFM and detection modules.

Figure 7-14 Association between CFM and detection modules

The following example illustrates fault information advertisement between CFM and detection modules over the path SwitchA -> SwitchB -> SwitchC -> SwitchF, as described in Table 7-6.

Table 7-6 Association between CFM and detection modules

Function Deployment

Issue to Be Resolved

Solution

CFM is deployed between SwitchB and SwitchC.

  • When CFM detects a fault in the link between SwitchB and SwitchC, SwitchF cannot detect the fault and still sends user traffic to SwitchC.

  • When Port1 fails, SwitchA cannot detect the fault and still sends user traffic to SwitchC.

CFM can be associated with Port1.

When CFM detects a fault, it instructs the OAMMGR module to disable and enable Port1 intermittently or make Port1 in Down state so that other modules can detect the fault.

EEM is deployed between SwitchA and SwitchB, and CFM is deployed between SwitchB and SwitchC.

Although CFM detects a fault on a network, CFM cannot notify SwitchA of the fault. As a result, SwitchA still forwards user traffic to the faulty link, causing a traffic interruption.

EFM can be associated with CFM.

  • When EFM detects a fault, it notifies CFM of the fault.

  • When CFM detects a link fault, it notifies EFM of the fault.

When the intermediate link fails, the fault can be notified to the remote device and an alarm is sent to the NMS. A network administrator analyzes alarm information to learn the link status and takes measures to rectify the fault.

CFM is between SwitchB and SwitchC and between SwitchC and SwitchF.

  • When CFM detects a fault in the link between SwitchC and SwitchF, SwitchA cannot detect the fault and still sends user traffic to SwitchC.

  • When CFM detects a fault in the link between SwitchB and SwitchC, the network device cannot detect the fault and still forwards network traffic to the faulty link.

Association between CFM modules can be configured.

When the CFM module detects a fault, it instructs the OAMMGR module to notify the other CFM module of the fault and sends an alarm to the NMS. A network administrator analyzes alarm information to learn the link status and takes measures to rectify the fault.

CFM is deployed between SwitchB and SwitchC, and BFD is deployed between SwitchC and SwitchF.

  • When a fault occurs in the link between SwitchB and SwitchC, the network device cannot detect the fault and still sends network traffic to the faulty link.

  • When a fault occurs in the link between SwitchC and SwitchF, SwitchA cannot detect the fault and still sends user traffic to the faulty link.

Association between CFM and BFD can be configured:

  • When CFM detects a fault, it notifies BFD of the fault.

  • When BFD detects a fault, it notifies CFM of the fault.

When the intermediate link fails, the fault can be notified to the remote device and an alarm is sent to the NMS. A network administrator analyzes alarm information to learn the link status and takes measures to rectify the fault.

Association Between CFM and Application Modules

The OAMMGR module can associate CFM with application modules. Currently, CFM can be associated with VRRP, as shown in Figure 7-15.

Figure 7-15 Association between CFM and application modules

The following example illustrates fault information advertisement between CFM and application modules over the path SwitchA -> SwitchB -> SwitchC -> SwitchF, as described in Table 7-7.

Table 7-7 Association between CFM and application modules

Function Deployment

Issue to Be Resolved

Solution

VRRP is deployed between SwitchB and SwitchC and between SwitchB and SwitchD, and CFM is deployed between SwitchC and SwitchF.

  • When a fault occurs in the link between SwitchB and SwitchC, SwitchF cannot detect the fault and still forwards network traffic to SwitchC.

  • When a fault occurs in the link between SwitchC and SwitchF, VRRP cannot detect the fault and user traffic is still sent to SwitchC.

Association between CFM and VRRP can be configured.

  • When CFM detects a link fault, the fault is notified to VRRP.

  • When VRRP detects a link fault, the fault is notified to CFM.

When the intermediate link fails, the fault can be notified to the remote device and an alarm is sent to the NMS. A network administrator analyzes alarm information to learn the link status and takes measures to rectify the fault.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075366

Views: 14671

Downloads: 35

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