[j-nsp] EVPN - BGP attribute propagation on MXes

[Richard McGovern]

Adam, sorry to disagree but I have a number of very successful EVPN/VXLAN deployments, all running 18.1R3-S[something].  Yes EVPN is new, but becoming more and more a Junos standard deployment every day.  At least IMHO.  Documentation needs a lot of catching up, so today some form of PS engagement by either Juniper [knowledgeable] Partner or Juniper PS often needed.

As for Type 5, this command maybe needed.  This depends on specific platform, but can be set on all without any concern:

set routing-options forwarding-table chained-composite-next-hop ingress evpn

This is pre-19.1.  From 19.1forward  this should be a Junos-default setting for all platforms that support EVPN.

HTH, Rich

Richard McGovern
Sr Sales Engineer, Juniper Networks 
978-618-3342
 
I’d rather be lucky than good, as I know I am not good
I don’t make the news, I just report it
 

On 7/3/19, 2:36 AM, "adamv0025 at netconsultings.com" <adamv0025 at netconsultings.com> wrote:

    > Guillermo Fernando Cotone
    > Sent: Monday, July 1, 2019 3:39 PM
    > 
    > Hi folks,
    > 
    > Does anyone have implemented BGP attribute propagation using EVPN
    > route type-5?
    > We're trying to get BGP community propagation over an EVPN L3VNI, but so
    > far we had no luck. I've no idea if there's any knob to enable this.
    > 
    > Our use-case is to connect BGP islands through an EVPN backbone, and we
    > expect BGP attributes, such as communities, to be propagated over the
    > backbone. Pretty much standard IP-VPN behavior. Also referenced here:
    > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Drabadan-2Dsajassi-2Dbess-2Devpn-2Dipvpn-2D&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=cViNvWbwxCvdnmDGDIbWYLiUsu8nisqLYXmd-x445bc&m=T6w2urFHFvXBxD29C0gFgfVkJh4B5x15Sv7j8BgLnFE&s=eJazdQ5Wm-axp47OtXLhuRBSVptRcnwDteGnYIacfRg&e= 
    > interworking-02#section-4.2
    > 
    > I'm not sure if this is actually supported on Juniper. We're running
    17.3R3-
    > S2.2.
    > 
    I'm sorry, we discovered too many "you're router might explode TM" bugs in
    the recent SURR (again) so nope still don't feel at all comfortable to run
    EVPN on Junos in production.
    This is our 3rd code upgrade over the years where we're trying to get EVPN
    working as its supposed to, but I'm starting to think that Juniper is just
    not the right vendor for running EVPN, they will get there eventually, just
    not ready, still.
    
    adam