Nessuna risorsa pertinente trovata nella lingua selezionata.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Configuration Guide - Reliability

S7700 and S9700 V200R011C10

This document describes the configuration of BFD, DLDP, VRRP, SmartLink, CFM, EFM, Y.1731 and MAC swap loopback to ensure reliability on the device.
Rate and give feedback:
Huawei utilizza la traduzione automatica insieme alla revisione umana per tradurre questo documento in diverse lingue, per facilitare la comprensione del contenuto di questo documento. Nota: la traduzione automatica, anche la più avanzata, non può corrispondere alla qualità dei trasduttori professionisti. Huawei non accetta alcuna responsabilità per l'accuratezza della traduzione e raccomanda di fare riferimento al documento inglese (per il quale è stato fornito un collegamento).
Creating an MA

Creating an MA


CFM detects connectivity faults on a direct or end-to-end link. As shown in Figure 9-17, 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-17  MAs in the MD

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

The mappings between MAs and service instances are described as follows.

Table 9-10  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. Associations between MAs and service instances are different in different networking, as shown in Figure 9-17.

  • On all devices of Layer 2 VLAN, VPLS, or VLL 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. See Creating a MEP for details of indirect association between MAs and service instances.


  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.

    ITU-T Y.1731 defines CCMs in ICC-based format. The ICC-based format is similar to the format of CCMs defined in IEEE802.1ag except for some fields. To be compatible with CCMs in ICC-based format, specify iccbased-ma-format-name.

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

    Table 9-11  MA configurations in different networking


    Configuration Procedure

    Detecting the directly connected link between Layer 2 interfaces on both devices

    You do not need to associate MAs with service instances.

    Detecting the end-to-end networking in a VLAN scenario

    Create an MA on a Layer 2 device.

    Run map vlan vlan-id

    The MA is associated 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-09-23

N. documento: EDOC1000178318


Download: 81

Average rating:
This Document Applies to these Products
Documenti correlati
Related Version
Precedente Avanti