Re: [j-nsp] EX2300 Code

A note on that. Not only does the switch stop responding and needs to be power cycled, but in our case while this happens uplink ports on a redundant ring bridge BPDUs from working switches and you get a nice linerate traffic loop going. We also use those as OOB management for our MX routers

Re: [j-nsp] Rock-solid JUNOS for QFX5100

I'd like to add to that, l2circuit hot standby needs 18+ to work, I had been waiting for some time now for 18 to be recommended to use it. Thanks for the info much appreciated! -phil -Original Message- From: Richard McGovern Sent: August 13, 2019 10:30 AM To: Philippe Girard ; Ross

Re: [j-nsp] Rock-solid JUNOS for QFX5100

Hi Ross We've recently switched our 5100s to 18.1R3-S5. 18.1 is stable with BGP/OSPF/LDP/RSVP/MPLS and LACP LAG in general. We don't use STP of any kind with the QFXs so I can't really help there. I was hesitant to upgrade to 18.X since the 5100 was still the only QFX not to have and 18

Re: [j-nsp] l2circuit between QFX-5110 & MX204 - one way traffic

Hello Some important information: Top level encapsulation flex-eth and flex-vlan-tagging is not supported on QFabric (QFX family) devices. That means you can't use a port that does ccc with any other type of encap, i.e. vlan-bridge, ext-vlan-br, or set family inet on a unit. Only MX with trio

Re: [j-nsp] Tail drop on EX3400

I have no idea of the actual increase this will generate. My guess is that I'll have to create a custom scheduler and apply to interfaces to be able to have all that buffer space available for basic Internet... - Philippe Girard On Thu, May 30, 2019 at 9:27 AM Jason Healy wrote: > On

[j-nsp] Tail drop on EX3400

-of-service? Would it avoid dedicating 100% of something to just one direction? I've asked all of those questions but I can't seem to get a clear answer. Thanks for your help. - Philippe Girard ___ juniper-nsp mailing list juniper-nsp@puck.nether.net

Re: [j-nsp] Junos 18.X on QFX5100

Thanks everyone for the advice, I went with 18.1R3-S5, it's been pretty stable and I didn't see any CPU abuse so far. - Philippe Girard 514-895-0877 On Tue, May 28, 2019 at 8:31 AM Franz Georg Köhler wrote: > On Sun, May 26, 2019 at 03:15:48PM +0200, Thomas Bellman < > bell...@n

[j-nsp] Junos 18.X on QFX5100

Greetings Anyone running production Junos 18.X on QFX5100? JTAC recommended still says 17.3R3-S4 but I'd really like to jump to 18 for some new features it offers. Thanks for your help. - Philippe Girard ___ juniper-nsp mailing list juniper-nsp

Re: [j-nsp] VRF export/import of eBGP learned route

r 2.5 years+ and no issues. > > Happy to share if ever you want to refine your solution. > > Br, > Niall > > -Original Message- > From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf > Of > Philippe Girard > Sent: 29 June 2018 15:15 >

Re: [j-nsp] VRF export/import of eBGP learned route

Hello everyone Thank you so much for your suggestions. The solution in this case is to remove the autonomous-system statement completely from the routing-instance routing-options and apply the local-as statement under bgp with the private knob. protocols { bgp { local-as 456 loops 2

[j-nsp] VRF export/import of eBGP learned route

Grettings I'm setting up this VRF that hosts the full routing table. I have other peerings or remote PEs that import IX routes through eBGP as well. The problem resides on something TAC tells me is Juniper specific, which is to add my own internal ASN to the as-path when using vrf-import to get