A backbone Ethernet VPN (B-EVPN) instance is essential for a superstratum provider edge (SPE) in connecting to hierarchical virtual private LAN service (HVPLS) and provider backbone bridge Ethernet VPN (PBB-EVPN) networks.
During migration from an HVPLS network to a PBB-EVPN, HVPLS and PBB-EVPN will coexist for some time. To transmit traffic between HVPLS and PBB-EVPN networks, SPEs must have B-EVPN instances configured.
The system view is displayed.
A PBB-EVPN source address is configured.
A B-EVPN instance is created, and its view is displayed.
A description is configured for the B-EVPN instance.
Similar to a hostname or an interface description, a B-EVPN instance description helps you memorize the B-EVPN instance.
A route distinguisher (RD) is configured for the B-EVPN instance.
A B-EVPN instance takes effect only after the RD is configured. The RDs of different EVPN instances on an SPE must be different.
After being configured, an RD cannot be modified, but can be deleted. After you delete the RD of a B-EVPN instance, the VPN targets of the B-EVPN instance will also be deleted.
VPN targets are configured for the B-EVPN instance.
A VPN target is a BGP extended community attribute used to control the receiving and advertisement of EVPN routes. A maximum of eight VPN targets can be configured using a vpn-target command. To configure more VPN targets for an EVPN instance address family, run the vpn-target command several times.
A B-MAC address is configured in the B-EVPN instance view.
The configuration is committed.