Hey folks –
I’m playing around with the latest cEOS image 4.25.2F-20711308.4252F (engineering build) and its handling of VRFs within EVPN seems broken. Specifically around the importing and exporting of RTs. As an example, let’s say I have three VRFs:
Within BGP I have:
Basically, A is importing all VRFs so he can talk to them via the VXLAN data plane. Each of the other VRFs is importing ONLY A (and themselves) so that they can talk back to A. Normally and inherit to EVPN: VRF A should not become a transit VRF. In my example, B should not be able to see C’s routes and vice versa. It’s only if the imported-route bit is added to the end of the route-target export line, that a given VRF should re-advertise its imported EVPN routes to other VRFs. But, I don’t have that configured.
As it stands, in cEOS B and C can see each others’ routes via A. That makes using cEOS to model out EVPN stuff a bit difficult to use. Can the developers please get a handle on this and get it figured out? I know the VRF stuff within cEOS has been a bit sketchy over the past few releases. It looks like it still needs some work. :-)
Post your Answer
You must be logged in to post an answer.