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, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

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).
Creating an MA

Creating an MA


CFM detects connectivity faults on a direct or end-to-end link. In Figure 9-9, CFM is deployed between the CE and PE3 to detect connectivity of the link. PE3 is a Layer 2 device or a bridge between the Layer 2 device and Layer 3 device.

Figure 9-9  MAs in the MD

Before detecting faults, you need to create an MD to determine the detection range, and create an MA and bind the MA to a service instance. Multiple MAs can be configured in an MD. For example, MD1 is deployed on the network between the CE and PE3. You can create MA1 and MA2 in MD1 based on service types. An MA corresponds to and serves a service instance. The device supports only the VLAN service type.

The mapping between MAs and service instances is described as follows.

Table 9-4  Mapping between MAs and service instances



Direct link

When an MA such as MA1 is deployed on a direct link and both interfaces of the link are Layer 2 interfaces, the MA does not need to be bound to a service instance.

End-to-end link

When an MA such as MA2 is deployed on end-to-end networking, the MA needs to be bound to a service instance. Association between MAs and service instances is different in different networking, as shown in Figure 9-9.

  • On all devices of Layer 2 VLAN networking, MAs are directly associated with service instances.

  • On PE3, a service instance is specified for an MA when a MEP is created in the MA.

After an MA is associated with a service instance, packets from MPs in MAs carry the service instance tag. In addition, MPs in the MA can receive packets from other MPs in the same MA.

Direct association between MAs and service instances is used as an example. For details about indirect association between MAs and service instances, see Creating a MEP.


  1. Run system-view

    The system view is displayed.

  2. Run cfm md md-name

    The MD view is displayed.

  3. Run ma ma-name [ format { icc-based iccbased-ma-format-name | string ma-format-name } ]

    An MA is created and the MA view is displayed.

  4. Perform the following configurations based on networking and service types.

    Table 9-5  MA configurations in different networking

    Networking environment

    Configuration Procedure

    Direct link between Layer 2 interfaces on both devices

    You do not need to associate MAs with service instances.

    End-to-end networking in a VLAN scenario

    Create an MA on a Layer 2 device.

    Run the map vlan vlan-id command to associate an MA with a VLAN.

    By default, an MA is not associated with any VLAN.

    Create an MA on a device connecting the Layer 2 network to the Layer 3 network.

    When creating a MEP on a device connecting the Layer 2 network to the Layer 3 network, specify a VLAN. The VLAN is automatically associated with the MA. For details, see Creating a MEP.

Updated: 2019-08-12

Document ID: EDOC1100034076

Views: 64387

Downloads: 112

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next