Hi,
We are an SP and provide an MPLS L3VPN to a customer, classic full mesh type. For 2 of their sites, say siteA and siteB, the customer is migrating DC servers from A to B and wish to stretch VLANX across these sites where VLANX is the existing VLAN at siteA. However they also wish to maintain the existing connectivity over our L3VPN that exists between the 2 sites so that VLANX at siteA can also communicate with existing VLANs/networks at siteB. This is a temporary arrangement for the migration and the requirement is to keep the same single physical access circuit into our MPLS PEs at each site.
Currently from the customer's CEs (managed) we have eBGP running with just a default route towards our PE VRF interface at each site. Currently there are no VRFs on the CE at siteA, though they are supported and siteB CE has a VRF configured, for a voice service but the main data traffic is routed in global. There are also backup CEs and circuits at each site into our MPLS core.
We do EoMPLS/VPWS/Pseudowires for other customers though usually this is encapsulating all traffic coming into our PE interface towards the remote end and not having to cater for an existing L3 VPN service between 2 sites also.
I'd really appreciate any suggestions on the most straightforward way to accomplish this solution given it will be temporary.
Thanks in advance