Question about EVPN route types
Hi all, I got a question about what EVPN route types are supported already in the latest version. It looks like type-2, type-3, and type-5 are supported. Type-1, and type-4 are not yet. If it is true, any plan the missing types are going to be supported? Another quick question, the fpm/fpm_pb.c file looks empty. Is there a missing patch need to be patched? It will be very helpful if anyone can point to a brief example how fpm is used by a switch that has a hardware forwarding path? Thanks, Jay
I believe some vendors have plans for adding more evpn types. I cannot speak for them regarding their time schedules. For FPM build FRR with `--enable-fpm` added on the configure line. Zebra FPM has two choices for fpm forwarding netlink or protobuf forwarding. If you want protobuf, use '--enable-protobuf` in configure, else only netlink is used as a communication medium. To load the appropriate module use -M fpm:netlink or -M fpm:protobuf donald On Mon, Mar 26, 2018 at 5:27 PM, Jay Chen <jchen1@paloaltonetworks.com> wrote:
Hi all,
I got a question about what EVPN route types are supported already in the latest version. It looks like type-2, type-3, and type-5 are supported. Type-1, and type-4 are not yet. If it is true, any plan the missing types are going to be supported?
Another quick question, the fpm/fpm_pb.c file looks empty. Is there a missing patch need to be patched? It will be very helpful if anyone can point to a brief example how fpm is used by a switch that has a hardware forwarding path?
Thanks,
Jay
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
The relevant documentation for this is here: https://frrouting.org/user-guide/zebra.html#zebra-fib-push-interface On Mon, Mar 26, 2018 at 6:52 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
I believe some vendors have plans for adding more evpn types. I cannot speak for them regarding their time schedules.
For FPM build FRR with `--enable-fpm` added on the configure line. Zebra FPM has two choices for fpm forwarding netlink or protobuf forwarding. If you want protobuf, use '--enable-protobuf` in configure, else only netlink is used as a communication medium. To load the appropriate module use -M fpm:netlink or -M fpm:protobuf
donald
On Mon, Mar 26, 2018 at 5:27 PM, Jay Chen <jchen1@paloaltonetworks.com> wrote:
Hi all,
I got a question about what EVPN route types are supported already in the latest version. It looks like type-2, type-3, and type-5 are supported. Type-1, and type-4 are not yet. If it is true, any plan the missing types are going to be supported?
Another quick question, the fpm/fpm_pb.c file looks empty. Is there a missing patch need to be patched? It will be very helpful if anyone can point to a brief example how fpm is used by a switch that has a hardware forwarding path?
Thanks,
Jay
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Thank you, currently our potential customers seem immediate interest is type-2 (maybe type-3 too). if they need type-1, type-4 probably later phase (for multicast multi-home), we can develop too. We will sync up by then. Currently we just started integrate FRR (POC). Thanks, Jay On 3/26/18, 4:16 PM, "Donald Sharp" <sharpd@cumulusnetworks.com> wrote: The relevant documentation for this is here: https://urldefense.proofpoint.com/v2/url?u=https-3A__frrouting.org_user-2Dgu... On Mon, Mar 26, 2018 at 6:52 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote: > I believe some vendors have plans for adding more evpn types. I > cannot speak for them regarding their time schedules. > > For FPM build FRR with `--enable-fpm` added on the configure line. > Zebra FPM has two choices for fpm forwarding netlink or protobuf > forwarding. If you want protobuf, use '--enable-protobuf` in > configure, else only netlink is used as a communication medium. To > load the appropriate module use -M fpm:netlink or -M fpm:protobuf > > donald > > On Mon, Mar 26, 2018 at 5:27 PM, Jay Chen <jchen1@paloaltonetworks.com> wrote: >> Hi all, >> >> >> >> I got a question about what EVPN route types are supported already in the >> latest version. It looks like type-2, type-3, and type-5 are supported. >> Type-1, and type-4 are not yet. If it is true, any plan the missing types >> are going to be supported? >> >> >> >> Another quick question, the fpm/fpm_pb.c file looks empty. Is there a >> missing patch need to be patched? It will be very helpful if anyone can >> point to a brief example how fpm is used by a switch that has a hardware >> forwarding path? >> >> >> >> Thanks, >> >> Jay >> >> >> _______________________________________________ >> dev mailing list >> dev@lists.frrouting.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_lis... >>
Hi, You are welcome to bring some EVPN extended features, namely EVPN type 1 and EVPN type 4 Thanks, Philippe On Tue, Mar 27, 2018 at 4:49 AM, Jay Chen <jchen1@paloaltonetworks.com> wrote:
Thank you, currently our potential customers seem immediate interest is type-2 (maybe type-3 too). if they need type-1, type-4 probably later phase (for multicast multi-home), we can develop too. We will sync up by then. Currently we just started integrate FRR (POC).
Thanks, Jay
On 3/26/18, 4:16 PM, "Donald Sharp" <sharpd@cumulusnetworks.com> wrote:
The relevant documentation for this is here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__frrouting.org_user-2Dgu...
On Mon, Mar 26, 2018 at 6:52 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote: > I believe some vendors have plans for adding more evpn types. I > cannot speak for them regarding their time schedules. > > For FPM build FRR with `--enable-fpm` added on the configure line. > Zebra FPM has two choices for fpm forwarding netlink or protobuf > forwarding. If you want protobuf, use '--enable-protobuf` in > configure, else only netlink is used as a communication medium. To > load the appropriate module use -M fpm:netlink or -M fpm:protobuf > > donald > > On Mon, Mar 26, 2018 at 5:27 PM, Jay Chen <jchen1@paloaltonetworks.com> wrote: >> Hi all, >> >> >> >> I got a question about what EVPN route types are supported already in the >> latest version. It looks like type-2, type-3, and type-5 are supported. >> Type-1, and type-4 are not yet. If it is true, any plan the missing types >> are going to be supported? >> >> >> >> Another quick question, the fpm/fpm_pb.c file looks empty. Is there a >> missing patch need to be patched? It will be very helpful if anyone can >> point to a brief example how fpm is used by a switch that has a hardware >> forwarding path? >> >> >> >> Thanks, >> >> Jay >> >> >> _______________________________________________ >> dev mailing list >> dev@lists.frrouting.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_lis... >>
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Hi Jay, I'd say the same as Philippe. We at Cumulus are looking into the type-1 and type-4 route implementation, but welcome other efforts also. Cheers, Vivek On Tue, Mar 27, 2018 at 2:06 AM, Philippe Guibert < philippe.guibert@6wind.com> wrote:
Hi,
You are welcome to bring some EVPN extended features, namely EVPN type 1 and EVPN type 4 Thanks,
Philippe
On Tue, Mar 27, 2018 at 4:49 AM, Jay Chen <jchen1@paloaltonetworks.com> wrote:
Thank you, currently our potential customers seem immediate interest is type-2 (maybe type-3 too). if they need type-1, type-4 probably later phase (for multicast multi-home), we can develop too. We will sync up by then. Currently we just started integrate FRR (POC).
Thanks, Jay
On 3/26/18, 4:16 PM, "Donald Sharp" <sharpd@cumulusnetworks.com> wrote:
The relevant documentation for this is here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__ frrouting.org_user-2Dguide_zebra.html-23zebra-2Dfib- 2Dpush-2Dinterface&d=DwIBaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFW e5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=SU_xZPka- A2WpWQD4P7IFqQXwDxuo9qVwQAd-c1WIcU&s=EhNk5Ru9bF27ttPaQDHa0wwdnj9irB s7XMzveLSpXW8&e=
On Mon, Mar 26, 2018 at 6:52 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote: > I believe some vendors have plans for adding more evpn types. I > cannot speak for them regarding their time schedules. > > For FPM build FRR with `--enable-fpm` added on the configure line. > Zebra FPM has two choices for fpm forwarding netlink or protobuf > forwarding. If you want protobuf, use '--enable-protobuf` in > configure, else only netlink is used as a communication medium. To > load the appropriate module use -M fpm:netlink or -M fpm:protobuf > > donald > > On Mon, Mar 26, 2018 at 5:27 PM, Jay Chen < jchen1@paloaltonetworks.com> wrote: >> Hi all, >> >> >> >> I got a question about what EVPN route types are supported already in the >> latest version. It looks like type-2, type-3, and type-5 are supported. >> Type-1, and type-4 are not yet. If it is true, any plan the missing types >> are going to be supported? >> >> >> >> Another quick question, the fpm/fpm_pb.c file looks empty. Is there a >> missing patch need to be patched? It will be very helpful if anyone can >> point to a brief example how fpm is used by a switch that has a hardware >> forwarding path? >> >> >> >> Thanks, >> >> Jay >> >> >> _______________________________________________ >> dev mailing list >> dev@lists.frrouting.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. frrouting.org_listinfo_dev&d=DwIBaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFW e5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=SU_xZPka- A2WpWQD4P7IFqQXwDxuo9qVwQAd-c1WIcU&s=SV_20pt83P- 0JYpAhkGoz0lKCPHRJrjFRI4Flbv6X8I&e= >>
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
0 Reserved [RFC7432] 1 Ethernet Auto-discovery [RFC7432] 2 MAC/IP Advertisement [RFC7432] 3 Inclusive Multicast Ethernet Tag [RFC7432] 4 Ethernet Segment [RFC7432] 5 IP Prefix route (TEMPORARY - registered 2017-02-17, extension registered 2018-01-31, expires 2019-02-17) [draft-ietf-bess-evpn-prefix-advertisement] 6 Selective Multicast Ethernet Tag Route (TEMPORARY - registered 2017-09-25, expires 2018-09-25) [draft-ietf-bess-evpn-igmp-mld-proxy] 7 IGMP Join Synch Route (TEMPORARY - registered 2017-09-25, expires 2018-09-25) [draft-ietf-bess-evpn-igmp-mld-proxy] 8 IGMP Leave Synch Route (TEMPORARY - registered 2017-09-25, expires 2018-09-25) [draft-ietf-bess-evpn-igmp-mld-proxy] 9 Per-Region I-PMSI A-D route (TEMPORARY - registered 2017-02-17, extension registered 2018-02-14, expires 2019-02-17) [draft-ietf-bess-evpn-bum-procedure-updates] 10 S-PMSI A-D route (TEMPORARY - registered 2017-02-17, extension registered 2018-02-14, expires 2019-02-17) [draft-ietf-bess-evpn-bum-procedure-updates] 11 Leaf A-D route (TEMPORARY - registered 2017-02-17, extension registered 2018-02-14, expires 2019-02-17) [draft-ietf-bess-evpn-bum-procedure-updates] 12-255 Unassigned
On Mar 28, 2018, at 14:17, Vivek Venkatraman <vivek@cumulusnetworks.com> wrote:
Hi Jay,
I'd say the same as Philippe. We at Cumulus are looking into the type-1 and type-4 route implementation, but welcome other efforts also.
Cheers, Vivek
On Tue, Mar 27, 2018 at 2:06 AM, Philippe Guibert <philippe.guibert@6wind.com <mailto:philippe.guibert@6wind.com>> wrote: Hi,
You are welcome to bring some EVPN extended features, namely EVPN type 1 and EVPN type 4 Thanks,
Philippe
On Tue, Mar 27, 2018 at 4:49 AM, Jay Chen <jchen1@paloaltonetworks.com <mailto:jchen1@paloaltonetworks.com>> wrote:
Thank you, currently our potential customers seem immediate interest is type-2 (maybe type-3 too). if they need type-1, type-4 probably later phase (for multicast multi-home), we can develop too. We will sync up by then. Currently we just started integrate FRR (POC).
Thanks, Jay
On 3/26/18, 4:16 PM, "Donald Sharp" <sharpd@cumulusnetworks.com <mailto:sharpd@cumulusnetworks.com>> wrote:
The relevant documentation for this is here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__frrouting.org_user-2Dgu... <https://urldefense.proofpoint.com/v2/url?u=https-3A__frrouting.org_user-2Dguide_zebra.html-23zebra-2Dfib-2Dpush-2Dinterface&d=DwIBaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=SU_xZPka-A2WpWQD4P7IFqQXwDxuo9qVwQAd-c1WIcU&s=EhNk5Ru9bF27ttPaQDHa0wwdnj9irBs7XMzveLSpXW8&e=>
On Mon, Mar 26, 2018 at 6:52 PM, Donald Sharp <sharpd@cumulusnetworks.com <mailto:sharpd@cumulusnetworks.com>> wrote: > I believe some vendors have plans for adding more evpn types. I > cannot speak for them regarding their time schedules. > > For FPM build FRR with `--enable-fpm` added on the configure line. > Zebra FPM has two choices for fpm forwarding netlink or protobuf > forwarding. If you want protobuf, use '--enable-protobuf` in > configure, else only netlink is used as a communication medium. To > load the appropriate module use -M fpm:netlink or -M fpm:protobuf > > donald > > On Mon, Mar 26, 2018 at 5:27 PM, Jay Chen <jchen1@paloaltonetworks.com <mailto:jchen1@paloaltonetworks.com>> wrote: >> Hi all, >> >> >> >> I got a question about what EVPN route types are supported already in the >> latest version. It looks like type-2, type-3, and type-5 are supported. >> Type-1, and type-4 are not yet. If it is true, any plan the missing types >> are going to be supported? >> >> >> >> Another quick question, the fpm/fpm_pb.c file looks empty. Is there a >> missing patch need to be patched? It will be very helpful if anyone can >> point to a brief example how fpm is used by a switch that has a hardware >> forwarding path? >> >> >> >> Thanks, >> >> Jay >> >> >> _______________________________________________ >> dev mailing list >> dev@lists.frrouting.org <mailto:dev@lists.frrouting.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_lis... <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_listinfo_dev&d=DwIBaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=SU_xZPka-A2WpWQD4P7IFqQXwDxuo9qVwQAd-c1WIcU&s=SV_20pt83P-0JYpAhkGoz0lKCPHRJrjFRI4Flbv6X8I&e=> >>
_______________________________________________ dev mailing list dev@lists.frrouting.org <mailto:dev@lists.frrouting.org> https://lists.frrouting.org/listinfo/dev <https://lists.frrouting.org/listinfo/dev>
_______________________________________________ dev mailing list dev@lists.frrouting.org <mailto:dev@lists.frrouting.org> https://lists.frrouting.org/listinfo/dev <https://lists.frrouting.org/listinfo/dev>
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
Jeff, What do you mean? Anyone is welcomed to provide patch series to be innovative on these topics. IETF RFC / drafts are welcomed since the are the specs of the implementations but even better having proven code that allows to understand and play with the specs will help to build up solutions. I believe FRR has proven and demonstrated that it can be faster to support protocol extensions. Please? Thank you,
Vincent, Nothing in particular, what you see is IANA EVPN route type registry, stuff that potentially would need to be implemented. Types 6-11 are multicast related and perhaps less interesting for DC focused implementation. That’s all, Jeff
On Mar 29, 2018, at 00:12, Vincent Jardin <vincent.jardin@6wind.com> wrote:
Jeff,
What do you mean? Anyone is welcomed to provide patch series to be innovative on these topics.
IETF RFC / drafts are welcomed since the are the specs of the implementations but even better having proven code that allows to understand and play with the specs will help to build up solutions.
I believe FRR has proven and demonstrated that it can be faster to support protocol extensions.
Please?
Thank you,
participants (6)
-
Donald Sharp -
Jay Chen -
Jeff Tantsura -
Philippe Guibert -
Vincent Jardin -
Vivek Venkatraman