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 V200R013C00

This document describes the configurations of Reliability, including BFD Configuration, VRRP Configuration, NSR 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).
Configuring Association Between CFM and an Interface

Configuring Association Between CFM and an Interface

Context

A device that carries IP services is usually dual-homed to an IP network to improve network robustness and service reliability. As shown in Figure 9-18, CE1 connects to CE2 and CE4 through the active and standby links. To detect link connectivity, you can configure CFM between CE1 and CE4. When CFM detects a link fault, it will set the protocol status of the associated Port1 or Port2 to Down and fast switches services.

Figure 9-18  Association between CFM and interfaces

Table 9-14 lists association between CFM and interfaces and its usage scenarios.

A physical interface associated with CFM cannot be the one that CFM monitors. If CFM is associated with a physical interface that it monitors, the link is locked.

Table 9-14  Association between CFM and interfaces
Association Mode Usage Scenario Description

Association between CFM and a CFM-capable interface

As shown in Figure 9-18, when CFM detects that the link between CE1 and CE2 becomes faulty, association between CFM and CFM-capable Port1 can be configured so that traffic is switched from the active link to the standby link.

The association function is configured in the interface view and is unidirectional. That is, CFM is associated with an interface only when CFM detects a fault on the link.

If CFM detects a fault, the OAMMGR module shuts down and then starts Port1 after 7s so that other modules can detect the fault.

Association between CFM and a CFM-incapable interface

As shown in Figure 9-18, when CFM detects that the link between CE1 and CE3 becomes faulty, association between CFM and CFM-incapable Port2 can be configured so that traffic is switched from the active link to the standby link.
  • If only association between CFM and Port1 is configured, CE2 cannot detect a link fault between CE1 and CE3 and will continue to send return traffic along the link.

  • If CE3 does not support OAM, association between EFM and EFM-incapable Port2 can be configured to report link faults.

The association function is configured in the OAM management view and is bidirectional.
  • When CFM detects a fault, the physical status of the interface bound to CFM goes Down, speeding up route convergence of the upper-layer protocol.

  • When the interface associated with CFM goes Down, it instructs the OAMMGR module to notify the CFM module of the fault. CFM then notifies the remote device of the fault.

Pre-configuration Tasks

Before associating CFM with an interface, perform the task of Configuring Basic Ethernet CFM Functions.

Procedure

  • Configuring association between CFM and a CFM-capable interface

    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 cfm md md-name ma ma-name remote-mep mep-id mep-id trigger if-down

      CFM is associated with an interface.

      By default, CFM is not associated with any interface.

    4. (Optional) Run cfm if-down trigger ccm-send-stop

      The MEP on an interface is triggered to stop sending CCMs when the interface goes Down.

      By default, the MEP on an interface is not triggered to stop sending CCMs when the interface goes Down.

      In a VLAN stacking scenario with an inward-facing MEP configured, if the interface where the MEP resides goes Down, to prevent the MEP from continuing to send CCMs so that other services can detect the fault information detected by CC, run the cfm if-down trigger ccm-send-stop command in the interface view.

  • Configuring association between CFM and a CFM-incapable interface

    1. Run system-view

      The system view is displayed.

    2. Run oam-mgr

      The OAM management view is displayed.

    3. Association between EFM and an EFM-incapable interface is bidirectional. Choose a configuration solution according to Table 9-15.

      Table 9-15  Association between Ethernet CFM and an interface

      Scenario

      Configuration Solution

      Faults need to be transmitted bidirectionally between Ethernet CFM and an interface.

      Choose either of the following commands (the two commands have the same function):

      • If you prefer to specify the MD and MA before the interface, use the oam-bind cfm md ma trigger if-down interface command.

      • If you prefer to specify the interface before the MD and MA, use the oam-bind interface cfm md ma trigger if-down command.

      Faults need to be transmitted unidirectionally between Ethernet CFM and an interface.

      To configure an interface to report faults to Ethernet CFM, use the oam-bind ingress interface egress cfm md ma trigger if-down command.

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065868

Views: 18644

Downloads: 11

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