[j-nsp] EVPN-VXLAN: Mixing QFX and EX

[Richard McGovern]

Correction - QFX5110 can now route VLAN/IP to VNI via this configuration:

https://www.juniper.net/documentation/en_US/junos/topics/concept/evpn-vxlan-qfx5110-l2-vxlan-l3-logical.html

I was no aware this information had been put out there.  Min SW would be 17.3R3, but 18.1R3-S[latest, now 4] would be recommended.

Please also note this functionality is not yet 100% supported as a Border Leaf for EVPN/VXLAN, so full "support" may not be yet available, despite the documentation.  I think this may be major reason this support has not yet been announced.  At least as far as I know, outside of this one link, I believe this is not announced or documented anywhere else.

Today I am using only 10K or MX as Border Leaf.

FYI


Richard McGovern
Sr Sales Engineer, Juniper Networks 
978-618-3342
 

On 4/16/19, 4:09 PM, "Richard McGovern" <rmcgovern at juniper.net> wrote:

    5110, can NOT route between VLAN/IP and VXLAN, today.  This is a future (some 19.x?).
    
    I do believe that QFX5110 is not really "certified" as a EVPN/VXLAN Spine.  Your design is what Juniper refers to as CRB - Centralized Route/Bridged.  That is, VXLAN L3 at the core, versus the edge.  The core is generally an IP Fabric.  
    
    Do matter what, you would need either MX or QFX10K model to talk to outside IP world, at least today.  You could talk server to server with your DC, but not outside, which I assume is not what you want.
    
    Rich
    
    Richard McGovern
    Sr Sales Engineer, Juniper Networks 
    978-618-3342
     
    
    On 4/16/19, 9:37 AM, "Vincent Bernat" <bernat at luffy.cx> wrote:
    
         ❦ 16 avril 2019 11:04 +00, Ian <i2vanov at protonmail.com>:
        
        > Thank you, Vincent.
        >
        > That is weird; it was a very simple layout illustration, I am attaching it again.
        >
        > Ultimate goal is to reduce broadcast domain size while having the
        > resources be able to participate in L2 without over-sizing it and
        > without using spanning-tree overheads and its risks.
        
        OK. So, the main question is whatever you are expecting to route between
        VXLAN (or between a VXLAN and a VLAN). EX4600 is only able to do L2
        stuff with VXLAN. 5110 is able to route between VXLAN and may be able
        under some conditions to route between a VLAN and a VXLAN.
        -- 
        10.0 times 0.1 is hardly ever 1.0.
                    - The Elements of Programming Style (Kernighan & Plauger)