evpn binding vpn-instance (Bridge domain view)

Usage Scenario

An EVPN instance can be bound only to BDs. To bind an EVPN instance to a BD, run the evpn binding vpn-instance command. 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 you want to implement the VLAN-aware function that allows different VLANs to access the same EVPN instance and isolate the BDs to which the VLANs belong, specify the bd-tag parameter when you bind the EVPN instance to the BDs. On devices at both ends of an EVPN, the same BD tag must be configured for the EVPN instance bound to a BD.

Prerequisites

If you use the VNI mode, ensure that a VNI has been created and associated with a BD and forwarding in split horizon mode has been enabled for a VXLAN tunnel using the vxlan vni split-horizon-mode command.

Precautions

The ways for binding an EVPN instance to a BD are mutually exclusive. To switch a binding way, remove the existing binding relationship and establish another binding relationship.

An EVPN instance has been bound in the BD view. Running the evpn binding vpn-instance command in the BD view to bind another EVPN instance will overwrite the current binding relationship.

If a VSI with a PW tag or a VSI with a Spoken PW configured has been bound to a BD, the evpn binding vpn-instance command cannot be run to bind an EVPN instance to the BD.