As described in Configuring EVPN-VXLAN and EVPN-MPLS in the Same VPLS/R-VPLS Service, two BGP instances are supported in VPLS services, where one instance can be associated with the EVPN-VXLAN and the other instance with the EVPN-MPLS. In addition, both BGP instances in a VPLS/R-VPLS service can also be associated with EVPN-VXLAN.
For example, a VPLS service can be configured with two VXLAN instances that use VNI 500 and 501 respectively, and those instances are associated with different BGP instances:
*A:PE-2# configure service vpls 500
*A:PE-2>config>service>vpls# info
----------------------------------------------
vxlan instance 1 vni 500 create
exit
vxlan instance 2 vni 501 create
exit
bgp
route-distinguisher 192.0.2.2:500
vsi-export "vsi-500-export"
vsi-import "vsi-500-import"
exit
bgp 2
route-distinguisher 192.0.2.2:501
vsi-export "vsi-501-export"
vsi-import "vsi-501-import"
exit
bgp-evpn
incl-mcast-orig-ip 23.23.23.23
evi 500
vxlan bgp 1 vxlan-instance 1
no shutdown
exit
vxlan bgp 2 vxlan-instance 2
no shutdown
exit
exit
stp
shutdown
exit
no shutdown
----------------------------------------------
From a data plane perspective, each VXLAN instance is instantiated in a different implicit SHG, so that traffic can be forwarded between them.
At a control plane level, the processing of MAC or IP routes and inclusive multicast routes is described in BGP-EVPN Routes in Services Configured with Two BGP Instances with the differences described in BGP-EVPN Routes in Multi-Instance EVPN-VXLAN Services.
The following features are not supported along with dual BGP instance EVPN-VXLAN services:
I-VPLS, B-VPLS, M-VPLS, and E-Tree service types
BGP-VPLS
EVPN ES association to VXLAN instance 1 when instance 2 is VXLAN and not MPLS
SAPs and SDP bindings when BGP instance 1 and BGP instance 2 are both associated with VXLAN
ESI-based PBR on the VPLS service
IGMP, MLD, and PIM-snooping
In addition, multi-instance EVPN-VXLAN services support:
Assisted-replication for IPv4 VTEPs in both VXLAN instances, where a single assisted-replication IPv4 address can be used for both instances.
Non-system IP and IPv6 termination, where a single vxlan-src-vtep ip-address can be configured for each service, and therefore used for the two instances.