> Saku Ytti
> Sent: Wednesday, September 2, 2020 8:37 AM
>
> On Wed, 2 Sep 2020 at 10:23, Andrew Alston
> wrote:
>
> > 2. Start looking at the new features - decide what may be useful -
> > if anything - and start testing to that to death - again preferably
> > before release so that the
On 2/Sep/20 09:37, Saku Ytti wrote:
> How do people measure this? Vendors spend tens or hundreds millions
> annually on testing, and still deliver absolute trash NOS, to every
> vendor, and there is no change that I can observe +20 years in
> quality. Basic things are broken, and everyone
--- Begin Message ---
> On Sep 2, 2020, at 3:37 AM, Saku Ytti wrote:
>
> I don't think vendors sit in scary skull towers and plans for shit
> NOS, I think it's emergent behaviour from how the market is modelled.
> And there are ways I think the market could change, but I'm already
> venturing
Thanks ytti
We still test drive a used car before purchasing, even though, the real test
will be how it perform all day long up and down the highway...day after day.
Yeah I don't test at scale for pps, and load of any and every protocol. Geez,
that's a lot of testing. I think IXIA and
Agreed. I like your philosophy about network software upgrades. if you
don't absolutely need to, then don't. I don't like to change my network if
it's running along just fine.
Another reason for upgrades is that a vendor is no longer going to work with
you because of EoS code. I've had that
Vicknair ; Roger Wiklund
; Colton Conor ; Juniper List
Subject: Re: [j-nsp] How to pick JUNOS Version
On Wed, 2 Sep 2020 at 10:23, Andrew Alston
wrote:
> 2. Start looking at the new features - decide what may be useful -
> if anything - and start testing to that to death -
On Wed, 2 Sep 2020 at 10:23, Andrew Alston
wrote:
> 2. Start looking at the new features - decide what may be useful - if
> anything - and start testing to that to death - again preferably before
> release so that the fixes can be in when it is released
How do people measure this? Vendors
] How to pick JUNOS Version
Thanks Kody, 2 questions sir... I recently began moving towards that same
version (17.4R2-S11) as I was hitting PR1419761 high cpu.
1 - did you upgrade straight from 15.1x54D51 to 17.4R2-S11 , or did you take
an intermediate step? Asking since JTAC recently told me
'
Subject: RE: [j-nsp] How to pick JUNOS Version
*External Email: Use Caution*
1 -
https://link.edgepilot.com/s/6890e15f/hA34W4NyWUumQulQkNIdtw?u=https://kb.juniper.net/InfoCenter/index?page=content%26id=KB33988
(pretty sure that avoids the usb craziness, if memory serves me right, I think
Juniper
the static route for management out of the default inet.0 table
Goodluck!
-KV
-Original Message-
From: aar...@gvtc.com
Sent: Tuesday, September 1, 2020 5:34 PM
To: Kody Vicknair ; 'Roger Wiklund'
; 'Colton Conor'
Cc: 'Juniper List'
Subject: RE: [j-nsp] How to pick JUNOS Version
*Exte
the static route for management out of the default inet.0 table
Goodluck!
-KV
-Original Message-
From: aar...@gvtc.com
Sent: Tuesday, September 1, 2020 5:34 PM
To: Kody Vicknair ; 'Roger Wiklund'
; 'Colton Conor'
Cc: 'Juniper List'
Subject: RE: [j-nsp] How to pick JUNOS Version
*Exte
Thanks Kody, 2 questions sir... I recently began moving towards that same
version (17.4R2-S11) as I was hitting PR1419761 high cpu.
1 - did you upgrade straight from 15.1x54D51 to 17.4R2-S11 , or did you take
an intermediate step? Asking since JTAC recently told me that this was too
far of a
requesting this?
-KV
-Original Message-
From: juniper-nsp On Behalf Of
aar...@gvtc.com
Sent: Tuesday, September 1, 2020 3:17 PM
To: 'Roger Wiklund' ; 'Colton Conor'
Cc: 'Juniper List'
Subject: Re: [j-nsp] How to pick JUNOS Version
*External Email: Use Caution*
Amen to that. I recall
Amen to that. I recall a few years back, going with 15.1X54-D51.7 for the
ACX5048 and having complete outage on irb's in L3VPN's with no dhcp relay
(ip helper) capability. ...and being baffled as I recall that the D51
version was on the JTAC recommended list. (D61 fixed it) So yeah, I agree
On 21/Aug/20 00:54, Giuliano C. Medalha wrote:
> ACX710 was officially launched this week.
>
> We are very excited about this new product. Working hard to have the right
> features for our market, especially H-QOS and FAT-PW quickly.
>
> In addition to this box has great cost benefit.
>
>
On 21/Aug/20 00:54, Giuliano C. Medalha wrote:
> ACX710 was officially launched this week.
>
> We are very excited about this new product. Working hard to have the right
> features for our market, especially H-QOS and FAT-PW quickly.
>
> In addition to this box has great cost benefit.
>
>
Good evening everyone
We have had some good experiences with the QFX5120-32C as a P router with MPLS
( 32 x 100G ) . It is running well on several clients in the last few days.
We had some problems with the initial code, mainly in network convergence and
null traffic in already formed tunnels,
-Original Message-
From: juniper-nsp On Behalf Of Mark Tinka
Sent: Thursday, August 20, 2020 11:38 AM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] How to pick JUNOS Version
it will be a reminder of what happened when Juniper went from JUNOS 8, and a
bit of 9, to Junos 10
On 20/Aug/20 15:33, Alexandre Guimaraes wrote:
> The best answer ever!
>
> Go to Vegas, in a Cassino, play some roulette. Wait for a number between 10
> and 20, if black, normal Junos, if red, SR Junos... if you lose all money
> before get a code similar a release, follow Tom Beecher
On 19/Aug/20 18:03, John Kristoff wrote:
> I'm not sure it is worth the time invested, but I'm probably a rare
> breed that reads through release notes and tries to determine what I'm
> in for or what I may have to change for an install or upgrade. It is
> very time consuming, but has been
On 19/Aug/20 17:12, Roger Wiklund wrote:
> I'm not sure how long Arista can keep the single binary approach as they
> expand their portfolio
> and feature set. For example it makes very little sense to have full BNG
> code on EX access switches, imge would be huge.
We've seen this play
On 19/Aug/20 17:00, Saku Ytti wrote:
> For the longest time Juniper pretended they had a single Junos,
> because they didn't have a large enough portfolio to justify anything
> else. Of course at very early of that marketing pitch the single image
> already included multiple images for
On 19/Aug/20 16:42, Colton Conor wrote:
> Just wondering if JUNOS will ever go to a unified code model like Arista
> does? The amount of PR's and bug issues in JUNOS seems overwhelming. Is
> this standard across vendors? I am impressed that Juniper takes the times
> to keep track of all these
00 Releases and Sub-Releases out
there that have to be "qualified" in order to get support
Just my 2ct
-- Christian
-Ursprüngliche Nachricht-
Von: juniper-nsp Im Auftrag von Alexandre
Guimaraes
Gesendet: Donnerstag, 20. August 2020 15:34
An: Tom Beecher ; Colton Conor
Cc:
The best answer ever!
Go to Vegas, in a Cassino, play some roulette. Wait for a number between 10
and 20, if black, normal Junos, if red, SR Junos... if you lose all money
before get a code similar a release, follow Tom Beecher schemas.
IT'S A LOTTERY to pick a junos release.
One of my
Once upon a time, John Kristoff said:
> I bet there is a generation of people on this list that never saw the
> cartoons Juniper ran in it's early days. There were probably some that
> weren't a dig at Cisco, but this was pretty representative as I recall.
I think I still have my deck of
Let’s be real... this is how to pick a new Junos version
https://fuckingjuniper.com/dice.gif
On Wed, Aug 19, 2020 at 12:32 PM Tom Beecher wrote:
> Start with the highest code version supported on the hardware that has all
>
> the features you need.
>
> Subtract 2 from the major revision number.
Start with the highest code version supported on the hardware that has all
the features you need.
Subtract 2 from the major revision number.
Pick a .3 version of that major revision.
Work towards current from there depending on test results, security needs,
etc.
On Wed, Aug 19, 2020 at 10:47 AM
On Wed, 19 Aug 2020 14:42:32 +
Colton Conor wrote:
> How do you plan which JUNOS version to deploy on your network? Do you stick
> to the KB21476 - JTAC Recommended Junos Software Versions or go a different
> route?
I've occasionally got some good advice from bigger operators who often
have
Agree with Rx-S and with reasonably conservative approach,
should be >= 3. In S1, S2 you will probably get PR fixes
affecting multiple previous releases but for a new R-specific PRs it
takes time to be discovered and fixes implemented, which usually takes
not less than 6 months. Also you may
Hi,
On 19.08.2020 16:42, Colton Conor wrote:
How do you plan which JUNOS version to deploy on your network? Do you stick
to the KB21476 - JTAC Recommended Junos Software Versions or go a different
route? Some of the JTAC recommended code seems to be very dated, but that
is probably by design
I'm not sure how long Arista can keep the single binary approach as they
expand their portfolio
and feature set. For example it makes very little sense to have full BNG
code on EX access switches, imge would be huge.
As for JTAC recommended release, it's a very generic recommendation not
taking
On Wed, 19 Aug 2020 at 17:47, Colton Conor wrote:
> Just wondering if JUNOS will ever go to a unified code model like Arista
> does? The amount of PR's and bug issues in JUNOS seems overwhelming. Is
For the longest time Juniper pretended they had a single Junos,
because they didn't have a large
How do you plan which JUNOS version to deploy on your network? Do you stick
to the KB21476 - JTAC Recommended Junos Software Versions or go a different
route? Some of the JTAC recommended code seems to be very dated, but that
is probably by design for stability.
34 matches
Mail list logo
