The statement that VPLS 10 must be configured with two BGP instances on the gateway PEs (PE3 and PE4) is false. A single BGP instance on a Nokia router is capable of handling multiple BGP address families simultaneously. In this scenario, a single BGP process can manage both the L2-VPN address family for BGP-VPLS signaling with the MPLS core and the EVPN address family for signaling with the VXLAN domain. The distinction is handled by configuring separate bgp and bgp-evpn contexts within the same VPLS service, not by creating separate, system-level BGP routing instances.

B. Using different Route Distinguishers (RDs) for the MPLS and VXLAN portions of the service on the gateway is required to uniquely identify and re-originate routes between the two domains.

C. Different Route Targets (RTs) are essential for the gateway to control the import/export of routes, effectively stitching the VPLS service between the separate MPLS and VXLAN signaling domains.

D. An export policy is required on the gateway PEs to control route propagation, ensuring that routes with encapsulation information for one domain (e.g., VXLAN) are not advertised into the other (MPLS).

1. Nokia 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Architecture Guide, Release 21.10.R1, Document Part Number: 3HE 17663 AAAC TQZZA, Edition 01.

Section: VPLS > EVPN for VPLS > EVPN-VXLAN to EVPN-MPLS Gateway.

Reference for A: The configuration examples in this section show a single router "Base" BGP instance. Within the VPLS service, separate bgp and bgp-evpn contexts are configured, demonstrating that multiple BGP instances are not required.

Reference for B & C: This section states, "The gateway is a VPLS service that is configured with a BGP context for the BGP-VPLS routes and a bgp-evpn context for the EVPN-VXLAN routes... When re-advertising routes from one protocol to the other, the gateway will use its own IP address as next-hop and generate a new route-distinguisher for the route." This confirms the need for separate contexts with their own RTs and the re-origination with new RDs.

Reference for D: The guide explains the gateway's role in handling BUM traffic by terminating an IMET route from one domain and originating a new one for the other (e.g., a PMSI attribute for MPLS). This controlled re-advertisement process necessitates policy control to prevent leaking incompatible encapsulation information.