To enable an EVPN to transmit Layer 3 services, configure an L3VPN instance and bind it to a VBDIF interface.
After this configuration, the L3VPN instance can manage host routes received from the VBDIF interface.
The system view is displayed.
For IPv4 services, configure an IPv4 L3VPN instance.
Run ip vpn-instance vpn-instance-name
A VPN instance is created, and its view is displayed.
Run ipv4-family
The VPN instance IPv4 address family is created, and its view is displayed.
Run route-distinguisher route-distinguisher
An RD is set for the VPN instance IPv4 address family.
Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ] evpn
One or multiple VPN targets are set for the VPN instance IPv4 address family.
The device is enabled to generate and advertise EVPN IP prefix routes and IRB routes.
(Optional) Run tnl-policy policy-name evpn
A specified tunnel policy is applied to the VPN instance IPv4 address family to associate the tunnel policy with the EVPN routes leaked to the VPN instance IPv4 address family.
(Optional) Run import route-policy policy-name evpn
An import route-policy is applied to the VPN instance IPv4 address family to filter EVPN routes to be imported to the VPN instance IPv4 address family. Perform this step to apply an import route-policy to the VPN instance IPv4 address family and set attributes for eligible EVPN routes. This enables the device to more precisely control EVPN routes to be imported into the VPN instance IPv4 address family more precisely.
(Optional) Run export route-policy policy-name evpn
An export route-policy is applied to the VPN instance IPv4 address family to filter EVPN routes to be advertised. Perform this step to apply an export route-policy to the VPN instance IPv4 address family and set attributes for eligible EVPN routes. This enables the device to more precisely control EVPN routes to be advertised.
Run quit
Exit the VPN instance IPv4 address family view.
Run quit
Exit the VPN instance view.
For IPv6 services, configure an IPv6 L3VPN instance.
Run ip vpn-instance vpn-instance-name
A VPN instance is created, and its view is displayed.
Run ipv6-family
The VPN instance IPv6 address family is created, and its view is displayed.
Run route-distinguisher route-distinguisher
An RD is set for the VPN instance IPv6 address family.
Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ] evpn
One or multiple VPN targets are set for the VPN instance IPv6 address family.
The device is enabled to generate and advertise EVPN IP prefix routes and IRB routes.
(Optional) Run tnl-policy policy-name evpn
A specified tunnel policy is applied to the VPN instance IPv6 address family to associate the tunnel policy with the EVPN routes leaked to the VPN instance IPv6 address family.
(Optional) Run import route-policy policy-name evpn
An import route-policy is applied to the VPN instance IPv6 address family to filter EVPN routes to be imported to the VPN instance IPv6 address family. Perform this step to apply an import route-policy to the VPN instance IPv6 address family and set attributes for eligible EVPN routes. This enables the device to more precisely control EVPN routes to be imported into the VPN instance IPv6 address family.
(Optional) Run export route-policy policy-name evpn
An export route-policy is applied to the VPN instance IPv6 address family to filter EVPN routes to be advertised. Perform this step to apply an export route-policy to the VPN instance IPv6 address family and set attributes for eligible EVPN routes. This enables the device to more precisely control EVPN routes to be advertised.
Run quit
Exit the VPN instance IPv6 address family view.
Run quit
Exit the VPN instance view.
A VBDIF interface is created, and the VBDIF interface view is displayed.
The VBDIF interface is bound to a VPN instance.
IPv6 is enabled on the interface.
An IPv4/v6 address is set for the VBDIF interface to implement Layer 3 communication.
A MAC address is configured for the VBDIF interface.
The device is enabled to advertise host ARP/ND routes and IRB/IRBv6 routes.
The configuration is committed.