[j-nsp] BPDUs over EVPN?
Seeing something "interesting" after an 18.1R3 to 18.4R1 upgrade on some EVPN PEs: the 18.4 boxes are now emitting BPDUs toward the CE interfaces containing pre-translation VLAN IDs from the CEs attached to remote PEs, which as far as I can tell are originating from the remote CE. Is EVPN expected to be forwarding BPDUs at all, intact or otherwise? If yes, is that dependent on how it's configured? In this case, it's VLAN-aware virtual switch instances everywhere, rewriting tags for multiple VLANs. Does PBB change things? We hit another bug where 18.1 was convinced these are PBB configs, when they're not... Given the discrepancy between releases, which one is wrong? I'm two weeks into a TAC case that's been passed around several times and still have no answers to any of these questions, would appreciate hearing from anyone who actually knows. Thanks! -Rob ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JunOS on EX4550?
On my EX4550, I recall going from 12 to 15 to get some mpls function. But I also recall having issues with mpls services and then later removing those mpls services. -Aaron -Original Message- From: Richard McGovern [mailto:rmcgov...@juniper.net] Sent: Thursday, October 17, 2019 5:27 AM To: Josh Baird Cc: Juniper List Subject: Re: [j-nsp] JunOS on EX4550? In my view best stability, used by most people (all of my customers are on 12.3 only), and no feature set differences. When 15.1 came out initially there were some concerns, so IMHO most just stayed on 12.3 once it was announced to have continued support. Just my 2 cents worth. Sent from my iPhone On Oct 17, 2019, at 12:01 AM, Josh Baird wrote: Thanks, Richard. Any particular reason why I would be better off using 12.3R12? On Wed, Oct 16, 2019 at 5:53 PM Richard McGovern mailto:rmcgov...@juniper.net>> wrote: No. For legacy EX switches, for which EX4500/EX4550 fall into, 15.1 is last release. At the same time, I think you might have best results using 12.3R12-S[latest] instead. Both 12.3 and 15.1 will be maintained for life of legacy EX switches. 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 10/16/19, 1:50 PM, "Josh Baird" mailto:joshba...@gmail.com>> wrote: Is it possible (and recommended) to run anything newer than 15.1 on EX4550 (which is what the JTAC-recommended version currently is). ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JunOS on EX4550?
--- Begin Message --- In my view best stability, used by most people (all of my customers are on 12.3 only), and no feature set differences. When 15.1 came out initially there were some concerns, so IMHO most just stayed on 12.3 once it was announced to have continued support. Just my 2 cents worth. Sent from my iPhone On Oct 17, 2019, at 12:01 AM, Josh Baird wrote: Thanks, Richard. Any particular reason why I would be better off using 12.3R12? On Wed, Oct 16, 2019 at 5:53 PM Richard McGovern mailto:rmcgov...@juniper.net>> wrote: No. For legacy EX switches, for which EX4500/EX4550 fall into, 15.1 is last release. At the same time, I think you might have best results using 12.3R12-S[latest] instead. Both 12.3 and 15.1 will be maintained for life of legacy EX switches. 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 10/16/19, 1:50 PM, "Josh Baird" mailto:joshba...@gmail.com>> wrote: Is it possible (and recommended) to run anything newer than 15.1 on EX4550 (which is what the JTAC-recommended version currently is). --- End Message --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] FlowSpec and RTBH
I see there are two questions here Marcin is asking: > I was wondering is there a way to export family flow routes (from > inetflow.0) to non flowspec BGP speaker? Q1 - Can I advertise Flowspec NLRIs to non Flowspec speakers ? The answer is clearly "No" > For example tag Flowspec route with community and advertise this route with > different community to blackhole on upstream network (selective RTBH). Q2 - Can flowspec be tagged with blackhole communities indicating the actions yet still using match criteria to apply those selectively. The answer is "Yes" the original 5575 RFC clearly allows so: A given flow may be associated with a set of attributes, depending on the particular application; such attributes may or may not include reachability information (i.e., NEXT_HOP). *Well-known or AS-specific community attributes can be used to encode a set of predetermined actions.* Thx, R. On Wed, Oct 16, 2019 at 8:44 PM Jeff Haas via juniper-nsp < juniper-nsp@puck.nether.net> wrote: > > > > -- Forwarded message -- > From: Jeff Haas > To: "Marcin Głuc" > Cc: "juniper-nsp@puck.nether.net" > Bcc: > Date: Wed, 16 Oct 2019 18:44:07 + > Subject: Re: [j-nsp] FlowSpec and RTBH > Marcin, > > > > On Oct 9, 2019, at 07:26, Marcin Głuc wrote: > > I was wondering is there a way to export family flow routes (from > > inetflow.0) to non flowspec BGP speaker? > > For example tag Flowspec route with community and advertise this route > with > > different community to blackhole on upstream network (selective RTBH). > > I'm having difficulty following your use case. > > Flowspec is its own address family with its own AFI/SAFI and a rather > nasty format. > > Are you asking that some internal component of a flowspec filter, like > destination, is leaked into another address family? > > -- Jeff > > > > > -- Forwarded message -- > From: Jeff Haas via juniper-nsp > To: "Marcin Głuc" > Cc: "juniper-nsp@puck.nether.net" > Bcc: > Date: Wed, 16 Oct 2019 18:44:07 + > Subject: Re: [j-nsp] FlowSpec and RTBH > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
