That helps. I had assumed that you had some L2 you needed to cross the MPLS network based on the MC-LAG and ESI-LAG design options. If you're strictly operating L3 at the core, then I'm with you completely in terms of complexity and would likely avoid any MC-LAG (or even ESI-LAG - the BLs could serve separate LAGs if you want since it's L3 termination). You likely already know this, but ensure you use IP-based RDs on the L3VPN for this use case to allow for multipath.
You've outlined what appear to be 3 valid designs, and what likely matters most at this point is the ease of you and others who would be responsible for this network to implement and manage it.
------------------------------
Jason Rokeach
------------------------------
Original Message:
Sent: 05-06-2021 08:56
From: Unknown User
Subject: Best option for physical connectivity
Good Day,
Thanks for the feedback. We will not be using EVPN signaling in the core MPLS network. Most services coming from the fabric will be offloaded into a L3VPN at the core.
Thanks,
Original Message:
Sent: 05-06-2021 08:33
From: Jason Rokeach
Subject: Best option for physical connectivity
Hi MFB,
Might I offer the suggestion that, since you're going to the effort in example 3 to use ESI LAG on the fabric side, you could also go ahead and use ESI LAG on the MPLS network? This could get you that active/active multihoming across the MPLS network, as it sounds like bandwidth is a concern. Depends on perspective, but you certainly could argue that this also reduces the complexity of example 3.
------------------------------
Jason Rokeach
Original Message:
Sent: 05-05-2021 07:20
From: Unknown User
Subject: Best option for physical connectivity
Good Day,
I have attached a diagram with 3 examples and would like to know which would be considered the best for physical connectivity between the fabric and core. The network consist of an MX MPLS core and then two data center fabrics. The fabric would be a combination of bridge overlay and routed bridge overlay at the BL. The fabric does not extend to the MX. The links are 10G and we are using AE not only for redundancy but the ability to increase the bandwidth. I feel example 3 is a no go do to possible complexity with using MCLAG etc. but from the other two examples would be the best for redundancy, traffic flow and removes complexity from the overall solution without compromising redundancy etc.