hey,
The switches doing it are two Arista 7050SX3 with a single instance
VXLAN EVPN. It should be a pretty simple setup. Not aware of any knobs
to modify any of this behavior or what we could be missing.
Hard to speak for Arista (we do also have EVPN-VXLAN implementation with
7050SX3 and A-A
Thanks for the response. It really doesn't bear directly on my situation,
but it does have references to what I need in RFC 8365.
Now that I know the terminology for these features, "Split Horizon" and
"Local Bias" (neither of which seems to fit very well to me), it's easier
to find more info.
I
hey,
"The EVPN split-horizon procedure ensures that the BUM traffic
originated by the multi-homed PE and sent from the non-DF to the DF, is
not replicated back to the CE (echoed packets on the CE). To avoid these
echoed packets, the non-DF (PE1) sends all the BUM packets to the DF
(PE2) with
My google-fu and attempts to dig through all of the standards is failing
me. I am trying to understand the mechanism to prevent an ESI designated
forwarder from looping BUM traffic.
The scenario I am imagining is BUM traffic coming into the fabric on an ESI
link on a non-designated member of the E
4 matches
Mail list logo
