Re: [j-nsp] juniper login down ?

I can login now. Weird , I couldn't login via cell phone or laptop on browser for several minutes... wonder if juniper.net was down. Seems ok now. -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net

[j-nsp] juniper login down ?

iam-sso.juniper.net - is this down ? - Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Channelizing a 40GbE port

Slight correction: There are three states for the fpc/pic/port channel-speed setting - This auto negotiates (and very poorly at that) 10g - This forces the qfx to expect four 10G links. (i.e. xe-0/0/49:0, xe-0/0/49:1 etc.) disable-auto-speed-detection - This forces the qfx to expect a 40G

Re: [j-nsp] Channelizing a 40GbE port

I thought that only controlled the overall speed of the port. But apparently it forces it to a breakout mode. Cool. Thanks. It seems a best practice is to disable auto-channelization and then force the 10g speed for any breakout? Jonathan From: Jason Healy

Re: [j-nsp] Channelizing a 40GbE port

On Feb 8, 2018, at 10:46 AM, Jonathan Call wrote: > > Juniper has instructions on how to disable auto-channelization on the QFX > series, but there doesn't appear to be a way to force (or even encourage) > channelization. I have a qfx5100-48t with a QSFP-40G-SR in port

[j-nsp] Channelizing a 40GbE port

Juniper has instructions on how to disable auto-channelization on the QFX series, but there doesn't appear to be a way to force (or even encourage) channelization. I have a qfx5100-48t with a QSFP-40G-SR in port 48 and a MTP-4xLC breakout cable connected to a couple of servers. The qfx5100-48t

Re: [j-nsp] Prefix independent convergence and FIB backup path

> Of Mark Smith > Sent: Thursday, February 08, 2018 12:02 PM > > Hi list, > > Test topology below. 2x MX80 with dual ip transit (full table ~600k prefixes). > TRA1 preferred over TRA2 (Localpref 200 set by PE1 import policy). Plain > unlabeled inet.0, no mpls in use. In lab topology both

Re: [j-nsp] Prefix independent convergence and FIB backup path

On Thu, Feb 8, 2018 at 3:42 PM, Olivier Benghozi wrote: > Here (VPNv4/v6, BGP PIC Core + PIC Edge, no addpath as not supported in vpn > AFI) we can see that, when possible: > active eBGP path is backuped via iBGP path > active iBGP path is backuped via another iBGP

Re: [j-nsp] Prefix independent convergence and FIB backup path

Here (VPNv4/v6, BGP PIC Core + PIC Edge, no addpath as not supported in vpn > AFI) we can see that, when possible: > No need for add-path in a VRF in fact. You always had it "for free" with per PE route-distinguishers. ___ juniper-nsp mailing list

Re: [j-nsp] Prefix independent convergence and FIB backup path

Hi Mark, Here (VPNv4/v6, BGP PIC Core + PIC Edge, no addpath as not supported in vpn AFI) we can see that, when possible: active eBGP path is backuped via iBGP path active iBGP path is backuped via another iBGP path We don't see: active iBGP backuped via inactive eBGP active eBGP backuped via

Re: [j-nsp] Prefix independent convergence and FIB backup path

Hi I did read through this thread before posting but it did not address my question. Thanks for pointer, though. For the other off-list reply, the loop lasts until FIB on PE2 is converged which is in the order of magnitude of minutes (maybe 10 depending on the prefix). On Thu, Feb 8, 2018 at

Re: [j-nsp] Prefix independent convergence and FIB backup path

Hi Mark- We had a long thread on a similar topic last spring, if you haven't browsed through this you may find it valuable. https://puck.nether.net/pipermail/juniper-nsp/2017-April/034145.html -Michael > -Original Message- > From: juniper-nsp