Re: [j-nsp] EVPN - no remote route of type EVPN in the L3VPN

Thanks guys, I got the solution from "MPLS In The SDN Era". On older software versions you need this: "set routing-options forwarding-table chained-composite-next-hop ingress evpn" The EVPN route uses "chained-composite-next-hop" and it is on by default in newer versions. Best regards Enoch Ny

Re: [j-nsp] EVPN - no remote route of type EVPN in the L3VPN

Forget 14.1R1. Go with 18.1R3-S6 and try again. /Roger On Wed, Jul 3, 2019 at 2:52 PM Enoch Nyatoti via juniper-nsp < juniper-nsp@puck.nether.net> wrote: > Hi guys, > I have a lab set up on EVE-NG to test EVPN. I am running version > 14.1R1.10. > > When my local PE router learns a new MAC/IP bin

Re: [j-nsp] Link establishment issues with 1Gbps SX/LX SFPs on QFX5110

Colton, EX Access switches used in Campus Fusion, do NOT run Junos. The run what we call SNOS (Satellite Network OS) instead. These SW releases, at least from a numbering standpoint, are completely different and independent of Junos releases. You can find Satellite SW via this direct link bel

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

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 engageme

[j-nsp] EVPN - no remote route of type EVPN in the L3VPN

Hi guys, I have a lab set up on EVE-NG to test EVPN. I am running version 14.1R1.10. When my local PE router learns a new MAC/IP binding it installs a host route in the IP VPN VRF with protocol type EVPN and a next hop of the VLAN’s IRB interface. This triggers the PE to transmit this host rout

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

Hi Alexander, Not really. BGP route propagation works and some attributes are preserved, e.g. as-path and local-preference, but not the attached communities. It looks like they are doing implicitly —in juniper syntax— "then community *set* EVPN-EXT-COMM" instead of "*add*" while importing BGP rout

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

Hello, On 01/07/2019 15:38, Guillermo Fernando Cotone wrote: 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://tools.ietf.org/