Hi Rob, You have effectively created L2 loop over EVPN, so to cut it you need a link between bridged network and EVPN to be a single link. There is no STP in EVPN. If you need two physical connections to between those networks, then LAG is a way to go. MC-LAG or virtual chassis can be configured on legacy switches to maintain that connection. ESI will handle that on EVPN side.
HTH, Wojciech czw., 18 kwi 2019, 08:37 użytkownik Rob Foehl <r...@loonybin.net> napisał: > On Thu, 18 Apr 2019, Krzysztof Szarkowicz wrote: > > > Hi Rob, > > RFC 7432, Section 8.5: > > > > If a bridged network is multihomed to more than one PE in an EVPN > > network via switches, then the support of All-Active redundancy mode > > requires the bridged network to be connected to two or more PEs using > > a LAG. > > > > > > So, have you MC-LAG (facing EVPN PEs) configured on your switches? > > No, hence the question... I'd have expected ESI-LAG to be relevant for > EVPN, and in this case it's not a single "CE" device but rather an entire > layer 2 domain. For a few of those, Juniper-flavored MC-LAG isn't an > option, anyway. In any case, it's not clear what 8.5 means by "must be > connected using a LAG" -- from only one device in said bridged network? > > -Rob > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp