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).
EFM Enhancements

EFM Enhancements

In compliance with EFM standards, EFM enhancements are extended EFM functions that include association between EFM and an EFM interface, active/standby extension, and single-fiber fault detection.

Association Between EFM and Interfaces

Association between EFM and EFM interfaces can set the associated interface in EFM Down state and trigger an active/standby link switchover, improving transmission quality and reliability.

In Figure 8-8, CE1 is dual-homed to CE2 and CE4. If the active link between CE1 and CE4 fails, traffic switches to the standby link between CE1 and CE2, minimizing the service interruption time.

Association between EFM and EFM interfaces that connect CE2 and CE4 to CE1 allows traffic to switch from the active link to the standby link if EFM detects a link fault or link quality deterioration. EFM detects one of the following events that occur on the link between CE1 and CE4 on the network shown in Figure 8-8:
  • Minor link event

  • Critical link event

  • EFM negotiation timeout

NOTE:
A device that carries IP services is usually dual-homed to an IP network to improve network robustness and service reliability.
Figure 8-8  Association between EFM and interfaces

EFM Active/Standby Extension

The EFM active/standby extension is implemented using the Vendor Specific Info field in the Local Information type-length-value (TLV) of an Information OAMPDU. The value of the Vendor Specific Info field indicates the master or backup state. Figure 8-9 shows the Vendor Specific Info field in an Information OAMPDU.

Figure 8-9  Vendor Specific Info field in an Information OAMPDU

The local device of an EFM connection supports the EFM active/standby extension. The remote device can parse the Vendor Specific Info field (carried in an Information OAMPDU) of the Local Information TLV sent by the local device. Value 0xAB in the Vendor Specific Info field indicates the master state and value 0xBA indicates the backup state. After receiving an Information OAMPDU, the remote device parses the OAMPDU and determines a traffic direction based on the master/backup status carried in the TLV.

The EFM active/standby extension is used together with EFM association functions to control the traffic direction. EFM can be associated with EFM interfaces and static routes destined for a network. The combination of functions allows traffic to automatically switch to a standby link if an active link fails, ensuring network reliability. In Figure 8-10, an interface on CE1 is connected to PE1 and another one is connected to PE2. EFM is associated with EFM interfaces or static routes destined for the network on PE1 and PE2. The association allows PE1 and PE2 to monitor active and standby status changes on CE1. If an active/standby interface switchover occurs on CE1, the EFM module notifies PE1 and PE2 of the status change. A traffic switchover is then implemented between PE1 and PE2. This process ensures that the upstream and downstream traffic travel along the same path. Table 8-7 lists implementation methods of EFM active/standby extension.

Figure 8-10  Implementation methods of EFM active/standby extension
Table 8-7  Implementations of the EFM active/standby extension

Implementation Method

Description

EFM active/standby extension used with association between EFM and EFM interfaces

If the EFM module on a PE detects an active/standby switchover on the SoftX device, the EFM module changes the status of the associated local EFM interface to trigger an active/standby link switchover. The service modules on the associated interface respond to the change by taking specific actions such as re-advertising routes.
  • After an EFM interface on the SoftX device enters the active state, the SoftX device notifies the PE of the status change. After receiving the notification, the PE notifies the interface associated with the EFM module of the status change. The associated interface goes Up, and services switch to this interface.

  • After an interface on the SoftX device enters the standby state, the EFM module notifies the PE of the status change. After receiving the notification, the PE notifies the interface associated with the EFM module of the status change. The associated interface goes Down and services switch to the interface that goes Up.

EFM active/standby extension used together with association between EFM and static routes

If the EFM module on a PE detects an active/standby switchover on the SoftX device, the EFM module instructs the routing management (RM) module to update the static route that is associated with the EFM module.

  • After an EFM interface on the SoftX device enters the active state, the EFM module notifies the PE of the status change. After receiving the notification, the EFM module on the PE instructs the RM module to generate a static route to the network.

  • After an EFM interface on the SoftX device enters the standby state, the EFM module notifies the PE of the status change. After receiving the notification, the EFM module on the PE instructs the RM module to delete the static route to the network.

Single-fiber Fault Detection

Optical interfaces work in full duplex mode and are considered Up as long as they receive packets even if they fail to send them. This may cause the working and physical statuses of an interface to be inconsistent.

In Figure 8-11, Optical Module A is directly connected to Optical Module B. If Line 2 is faulty, Optical Module B cannot receive packets and sets its physical status to Down. Optical Module A can still receive packets from Optical Module B over Line 1. Therefore, the physical status of Optical Module A is considered to be Up. If Optical Module A sends packets to Optical Module B, service interruption occurs because Optical Module B cannot receive packets.

Figure 8-11  EFM single-fiber fault detection

EFM single-fiber detection can be used to prevent the preceding problem.

After EFM is associated with an interface, the interface can go Down when EFM detects a single-fiber fault on the interface. EFM enables Layer 2 and Layer 3 services to detect the interface status change and trigger a service switchover. The working status and physical status of the interface remain consistent, preventing service interruption. After the fault is rectified and EFM negotiation succeeds, the interface goes Up and services switch back.

Single-fiber fault detection prevents inconsistency between the working status and physical interface status and allows the service modules to properly detect interface status changes.

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065868

Views: 15515

Downloads: 3

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