Building network automation solutions

9 module online course

Start now!

3 comments:

  1. Thanks for the update. So interoperability between vendors would still be a dream? Or is it on purpose?
    Replies
    1. Regardless of the sanity of trying to build a multi-vendor fabrics (let's not go there), EVPN seems to be pretty solid when it comes to L2-only forwarding in simple environments (IGP + IBGP). L3 is still a bit murky (asymmetric versus symmetric), as is multi-fabric behavior (changing next hops on fabric edge).

      The true "beauties" start when vendors try to persuade you to use "interesting" designs like running IBGP over EBGP for no good reason (apart from lock-in).
    2. Actually it works (depending on which IRB methods / evpn prefix adv the vendors support, like Ivan said). See interops test result from the MPLS Forum (2017) :

      http://www.eantc.de/fileadmin/eantc/downloads/events/2011-2015/MPLSSDNNFV_2017/EANTC-MPLSSDNNFV2017-WhitePaper-Final_v2.pdf

      Here is the latest that happened 1 month ago :

      http://www.eantc.de/fileadmin/eantc/downloads/events/2017-2020/MPLS2018/EANTC-MPLSSDNNFV2018-WhitePaper-final.pdf

      I tested in my lab interoperability between Arista & Cisco 9K just for fun (no reason to mix leaf/spine from different vendors I agree :) )
Add comment
Sidebar