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 routes into EVPN .
Best, Guillermo On Wed, Jul 3, 2019 at 10:55 AM Alexander Arseniev <arsen...@btinternet.com> wrote: > 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/html/draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02#section-4.2 > > I'm not sure if this is actually supported on Juniper. We're > running 17.3R3-S2.2. > > Are You terminating PE-CE BGP on IRB interface on PE side? This is > supported from 19.2R1 > > > https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/release-notes/19.2/jd0e4828.html#jd0e4903 > > Thanks > > Alex > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
