[FROG] New EVPN Code in Master
Mitesh Kanjariya
mitesh at cumulusnetworks.com
Wed Jan 17 13:39:54 EST 2018
Hi Rendo,
I checked the code. As Vivek mentioned, we are missing some commits which
unblocks "l2vpn evpn" under non-default VRFs. We should be getting those in
with the next PR within a few days.
On Tue, Jan 16, 2018 at 8:01 PM, Vivek Venkatraman <
vivek at cumulusnetworks.com> wrote:
> Hi Rendo,
>
> I'll let Mitesh check on and respond to why you are unable to configure
> the "advertise ipv4 unicast" command. It is possible some commit has been
> missed. We do have some additional fixes that Mitesh is in the process of
> submitting. In any case, the idea is to control the injection of EVPN
> type-5 routes using this command. We're going to support a route-map option
> also for it in an upcoming commit.
>
> Regarding advertising subnet routes for the locally configured subnets,
> we're having a rethink on the need for an additional command. The same can
> be achieved by redistributing connected routes of the VRF into BGP and then
> using the "advertise ipv4 unicast" command. Control for advertising
> specific subnets can be currently achieved through use of route-map for the
> redistribute command, and subsequently, using route-map for the "advertise"
> command. Our documents aren't updated yet as we haven't concluded on this,
> however, I recommend that you try out this approach as soon as the
> "advertise ipv4 unicast" command is working.
>
> Thanks,
> Vivek
>
> On Tue, Jan 16, 2018 at 7:09 PM, rendo <rendo.aw at gmail.com> wrote:
>
>>
>> Hi Mitesh,
>>
>> maybe i am missing something, looks like the cli reject it
>>
>> linux-93# conf t
>> linux-93(config)# router bgp 64000 vrf vrf-110
>> linux-93(config-router)# address-family l2vpn evpn
>> Only Unicast and Multicast SAFIs supported in non-core instances.
>> linux-93(config-router)#
>>
>>
>> and this is my vrf
>>
>> linux-93# show ip route vrf vrf-110
>> Codes: K - kernel route, C - connected, S - static, R - RIP,
>> O - OSPF, I - IS-IS, B - BGP, P - PIM, E - EIGRP, N - NHRP,
>> T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
>> > - selected route, * - FIB route
>>
>>
>> VRF vrf-110:
>> C>* 10.93.193.0/24 is directly connected, ens7, 2d01h49m
>> C>* 10.93.253.0/24 is directly connected, br110, 2d01h49m
>>
>>
>>
>> I also tried "advertise-subnet" as mentioned in cumulus doc, the command
>> is rejected too
>>
>> linux-93(config)# router bgp 64000
>> linux-93(config-router)# address-family l2vpn evpn
>> linux-93(config-router-af)# vni 20110
>> linux-93(config-router-af-vni)# advertise-subnet
>> % Unknown command.
>>
>>
>>
>> I tried few other thing, and this is my current config. It still the
>> same, my instance can receive RT 5 prefix, but it send nothing.
>>
>> vrf vrf-110
>> vni 20110
>> !
>>
>> ...
>>
>> router bgp 64000
>> coalesce-time 1000
>> neighbor 10.0.0.11 remote-as 64000
>> neighbor 10.0.0.11 update-source 10.0.0.93
>> !
>> address-family l2vpn evpn
>> neighbor 10.0.0.11 activate
>> vni 20110
>> rd 10.0.0.93:110
>> route-target import 64000:110
>> route-target export 64000:110
>> advertise-default-gw
>> exit-vni
>> vni 10100
>> rd 10.0.0.93:100
>> route-target import 64200:100
>> route-target export 64200:100
>> exit-vni
>> advertise-all-vni
>> advertise ipv4 unicast
>> exit-address-family
>> vrf-policy vrf-110
>> rd 10.0.0.93:901
>> rt both 64000:901
>> exit-vrf-policy
>> vnc defaults
>> exit-vnc
>> !
>> router bgp 64000 vrf vrf-110
>> coalesce-time 1000
>> !
>> address-family ipv4 unicast
>> network 0.0.0.0/0
>> redistribute kernel
>> redistribute connected
>> redistribute static
>> exit-address-family
>> !
>>
>>
>>
>> linux-93# show bgp l2vpn evpn
>>
>> ...
>> Route Distinguisher: ip 10.0.0.21:110
>>
>> *>i[5]:[0]:[24]:[10.21.121.0]
>> 10.0.1.21 0 100 0 ?
>> ...
>>
>>
>> *>i[5]:[0]:[24]:[10.25.125.0]
>> 10.0.0.25 100 0 i
>> Route Distinguisher: ip 10.0.0.93:100
>>
>> ...
>>
>>
>>
>> Thanks.
>>
>>
>> rendo
>>
>>
>>
>> On Tue, Jan 16, 2018 at 5:31 PM, Mitesh Kanjariya <
>> mitesh at cumulusnetworks.com> wrote:
>>
>>> Hi Rendo,
>>>
>>> You need to enable type-5 route advertisement. Please find an example
>>> below. The CLI in red will do the trick.
>>>
>>> router bgp <> vrf <>
>>>
>>> address-family l2vpn evpn
>>>
>>> advertise ipv4 unicast
>>>
>>> exit-address-family
>>>
>>> end
>>>
>>>
>>> For reference yo could follow: https://docs.cumulusne
>>> tworks.com/display/DOCS/Ethernet+Virtual+Private+Network+-+EVPN
>>>
>>> On Tue, Jan 16, 2018 at 2:02 PM, rendo <rendo.aw at gmail.com> wrote:
>>>
>>>> Hi Donald,
>>>>
>>>> Thanks for the update and thanks for everyone involved to make this
>>>> happen.
>>>>
>>>> Out of my curiosity, I did a quick test, and evpn type 2 looks very
>>>> good, both control plane and data plane works as expected.
>>>> For type 5, i can see my FRR is able to receive the prefix, but i could
>>>> not find a way to advertise my local prefix as type 5. Please let me know
>>>> if you have any doc/pointer for this.
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> rendo
>>>>
>>>>
>>>> On Sat, Jan 13, 2018 at 8:05 AM, Donald Sharp <
>>>> sharpd at cumulusnetworks.com> wrote:
>>>>
>>>>> All -
>>>>>
>>>>> EVPN control plane in FRR is now enhanced so that it supports both
>>>>> asymmetric and symmetric routing models. Prefix-based routing is also
>>>>> supported using EVPN type-5 routes. Also, with all routing models, L3
>>>>> multi-tenancy is inherently supported
>>>>>
>>>>> I'd like to thank Mitesh for his hard work getting this done!
>>>>>
>>>>> thanks!
>>>>>
>>>>> donald
>>>>>
>>>>> _______________________________________________
>>>>> frog mailing list
>>>>> frog at lists.frrouting.org
>>>>> https://lists.frrouting.org/listinfo/frog
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Mitesh
>>>
>>
>>
>
--
Regards,
Mitesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20180117/73c11012/attachment-0001.html>
More information about the frog
mailing list