Configuring a BD and Binding an EVPN Instance to the BD

An EVPN instance in BD mode is only bound to a BD instead of an interface.

Context

An EVPN instance can be bound to a BD in two ways: using a VXLAN Network Identifier (VNI) and using MPLS. In VNI mode, an EVPN instance is bound to a BD after a VNI is configured. In MPLS mode, an EVPN instance is bound to a BD directly in the BD view. If an EVPN instance needs to access a VPLS network, the EVPN instance must be bound to a BD in VNI mode.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bridge-domain bd-id

    The view of the BD to be bound to an EVPN instance is displayed.

  3. Run vxlan vni vni-id split-horizon-mode

    A VNI is created and bound to a BD, and split horizon is configured for packet forwarding.

  4. Run evpn binding vpn-instance vpn-instance-name [ bd-tag bd-tag ]

    The BD is bound to an EVPN instance. By specifying different bd-tag values, you can bind multiple BDs with different VLANs to the same EVPN instance and isolate services in these BDs.

  5. (Optional) Run mac-learn-style qualify

    The MAC address learning mode is set to qualify.

    If no MAC address learning mode is configured, each MAC address is unique in the BD, and the device learns MAC addresses based on BDs. VLAN-based differentiation is not needed in this case. If users need to be differentiated based on VLANs, perform this step to set the MAC address learning mode to qualify, so that each VLAN has its own MAC address space. The device learns MAC addresses based on both MAC addresses and VLAN tags carried in user Ethernet packets.

    This step is recommended when the VLAN-aware service model is used on the user side for EVPN access.

  6. (Optional) Run reserve-interface fast-switch enable

    The reserve-interface fast switching function is enabled.

    When the master interface board fails, you can perform this step to enable the fast switchover of reserved interfaces so that broadcast traffic can be quickly switched to the backup interface board.

  7. Run quit

    Return to the system view.

  8. Run interface interface-type interface-number.subnum mode l2

    A Layer 2 sub-interface is created, and the Layer 2 sub-interface view is displayed.

    Before running this command, ensure that the involved Layer 2 main interface does not have the port link-type dot1q-tunnel command configuration. If the configuration exists, run the undo port link-type command to delete it.

  9. Run encapsulation { dot1q [ vid low-pe-vid [ to high-pe-vid ] ] | untag | qinq [ vid pe-vid ce-vid { low-ce-vid [ to high-ce-vid ] | default } ] }

    The encapsulation type of packets allowed to pass through the interface is specified.

    If the MAC address learning mode is qualify, ce-vid used in QinQ encapsulation cannot be default.

  10. Run rewrite pop { single | double }

    The function to remove VLAN tags from received packets is enabled.

    For single-tagged packets that a Layer 2 sub-interface receives, specify single to enable the sub-interface to remove single VLAN tags from these packets.

    If the encapsulation type of packets has been set to QinQ in the previous step, specify double to enable the sub-interface to remove double VLAN tags from the received packets.

    If the current MAC address learning mode is qualify, this step cannot be performed.

  11. Run bridge-domain bd-id

    The Layer 2 sub-interface is added to the BD to transmit data packets through this BD.

  12. Run commit

    The configuration is committed.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >