Mailing List Archive

Junos OS Evolved
I was unaware of Junos OS Evolved until recently. At what version did
regular Junos evolve into Junos OS Evolved? Is there a certain version
where after that version, everything ongoing is Junos OS Evolved?
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
Hey Colton,

> I was unaware of Junos OS Evolved until recently. At what version did
> regular Junos evolve into Junos OS Evolved? Is there a certain version
> where after that version, everything ongoing is Junos OS Evolved?

I think EVO appeared in 19.1, but in most cases you don't have a
choice, you either install classic or you install evo. New platforms
already only have EVO options and older platforms only have classic
options.

--
++ytti
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
    Nice another round of customers doing JNP QA :(

-----
Alain Hebert ahebert@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

On 2020-10-09 12:38, Saku Ytti wrote:
> Hey Colton,
>
>> I was unaware of Junos OS Evolved until recently. At what version did
>> regular Junos evolve into Junos OS Evolved? Is there a certain version
>> where after that version, everything ongoing is Junos OS Evolved?
> I think EVO appeared in 19.1, but in most cases you don't have a
> choice, you either install classic or you install evo. New platforms
> already only have EVO options and older platforms only have classic
> options.
>

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
Like many things either it works or it doesn't. I'm not a fan of paying for software with bugs personally.

We do have Evo in use.

Sent from my iCar

> On Oct 9, 2020, at 12:55 PM, Alain Hebert <ahebert@pubnix.net> wrote:
>
> ? Nice another round of customers doing JNP QA :(
>
> -----
> Alain Hebert ahebert@pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
>
>> On 2020-10-09 12:38, Saku Ytti wrote:
>> Hey Colton,
>>
>>> I was unaware of Junos OS Evolved until recently. At what version did
>>> regular Junos evolve into Junos OS Evolved? Is there a certain version
>>> where after that version, everything ongoing is Junos OS Evolved?
>> I think EVO appeared in 19.1, but in most cases you don't have a
>> choice, you either install classic or you install evo. New platforms
>> already only have EVO options and older platforms only have classic
>> options.
>>
>
> _______________________________________________
> 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
Re: Junos OS Evolved [ In reply to ]
    Well this is coming from my experience with QFX5100, less of an
issue with MX platforms but still for the price tag it was kinda hellish.

    Been stable after we worked some of the pitfalls... still got some
chipset related issue when someone makes an error and mix L2 VLANs with
VLAN-CCC on the same interface.  Nothing like 3 lvl of peer review
cannot fix.

-----
Alain Hebert ahebert@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

On 2020-10-09 13:00, Jared Mauch wrote:
> Like many things either it works or it doesn't. I'm not a fan of paying for software with bugs personally.
>
> We do have Evo in use.
>
> Sent from my iCar
>
>> On Oct 9, 2020, at 12:55 PM, Alain Hebert <ahebert@pubnix.net> wrote:
>>
>> ? Nice another round of customers doing JNP QA :(
>>
>> -----
>> Alain Hebert ahebert@pubnix.net
>> PubNIX Inc.
>> 50 boul. St-Charles
>> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
>> Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
>>
>>> On 2020-10-09 12:38, Saku Ytti wrote:
>>> Hey Colton,
>>>
>>>> I was unaware of Junos OS Evolved until recently. At what version did
>>>> regular Junos evolve into Junos OS Evolved? Is there a certain version
>>>> where after that version, everything ongoing is Junos OS Evolved?
>>> I think EVO appeared in 19.1, but in most cases you don't have a
>>> choice, you either install classic or you install evo. New platforms
>>> already only have EVO options and older platforms only have classic
>>> options.
>>>
>> _______________________________________________
>> 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
Re: Junos OS Evolved [ In reply to ]
So is Junos OS Evolved available for the MX routers? How would you go from
regular Junos to Junos OS Evolved on a MX 240/480/960 for example?

On Fri, Oct 9, 2020 at 11:38 AM Saku Ytti <saku@ytti.fi> wrote:

> Hey Colton,
>
> > I was unaware of Junos OS Evolved until recently. At what version did
> > regular Junos evolve into Junos OS Evolved? Is there a certain version
> > where after that version, everything ongoing is Junos OS Evolved?
>
> I think EVO appeared in 19.1, but in most cases you don't have a
> choice, you either install classic or you install evo. New platforms
> already only have EVO options and older platforms only have classic
> options.
>
> --
> ++ytti
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
On Sun, 11 Oct 2020 at 00:24, Colton Conor <colton.conor@gmail.com> wrote:

> So is Junos OS Evolved available for the MX routers? How would you go from regular Junos to Junos OS Evolved on a MX 240/480/960 for example?

It is not, but expect to see it in future MX REs.



--
++ytti
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
Whats its history? (will Google it too)

I mean, from a software engineering point if view, it's a tough call to
start again.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
    Since most of the reference implementation from their ASIC provider
with be Linux based ... the path of least resistance wins.

    And, I think, the "preference" of the majority of their own
devs/mgmt which never knew nothing but Linux =D.

-----
Alain Hebert ahebert@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

On 2020-10-11 07:04, Gavin Henry wrote:
> Whats its history? (will Google it too)
>
> I mean, from a software engineering point if view, it's a tough call to
> start again.
> _______________________________________________
> 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
Re: Junos OS Evolved [ In reply to ]
Once upon a time, Alain Hebert <ahebert@pubnix.net> said:
> ??? Since most of the reference implementation from their ASIC
> provider with be Linux based ... the path of least resistance wins.

This is on the RE, which is just standard Intel x86 stuff (or IIRC ARM
for smaller stuff?).

> ??? And, I think, the "preference" of the majority of their own
> devs/mgmt which never knew nothing but Linux =D.

I think with FreeBSD-based Junos, Juniper forked their chosen FreeBSD
release and made a bunch of customizations. That means every time they
need to get to newer FreeBSD (for newer hardware support, newer
features, etc.), it is a major operation. With Junos Evolved, it sounds
like they're going with somebody else's distribution (Wind River) and
adapting to fit it. Then when they need new support, they just get the
latest release and go (somebody else does all the hardware work).

It's my understand that the Linux kernel tends to have broader support
for new hardware than the FreeBSD kernel, but I haven't really looked in
a long time (I run Linux, not FreeBSD, so I could be wrong).

--
Chris Adams <cma@cmadams.net>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
    I haven't unpackaged an Evolved distribution yet, but my experience
with WindRiver licensing back in early 2000, it would be pricey.

    As for FreeBSD, they could have gone the way of upgrading the
kernel (I saw some evidences about 10.x but no confirmation yet) but
depending of their initial work done during the 4.x days, switching
might have been a better financial choice.

    Device support wouldn't be an issue pretty much all the worthy
stuff works on both...  and with virtualization its not an really issue
anymore.

-----
Alain Hebert ahebert@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

On 2020-10-13 13:22, Chris Adams wrote:
> Once upon a time, Alain Hebert <ahebert@pubnix.net> said:
>>     Since most of the reference implementation from their ASIC
>> provider with be Linux based ... the path of least resistance wins.
> This is on the RE, which is just standard Intel x86 stuff (or IIRC ARM
> for smaller stuff?).
>
>>     And, I think, the "preference" of the majority of their own
>> devs/mgmt which never knew nothing but Linux =D.
> I think with FreeBSD-based Junos, Juniper forked their chosen FreeBSD
> release and made a bunch of customizations. That means every time they
> need to get to newer FreeBSD (for newer hardware support, newer
> features, etc.), it is a major operation. With Junos Evolved, it sounds
> like they're going with somebody else's distribution (Wind River) and
> adapting to fit it. Then when they need new support, they just get the
> latest release and go (somebody else does all the hardware work).
>
> It's my understand that the Linux kernel tends to have broader support
> for new hardware than the FreeBSD kernel, but I haven't really looked in
> a long time (I run Linux, not FreeBSD, so I could be wrong).
>

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
On Tue, Oct 13, 2020 at 01:51:59PM -0400, Alain Hebert wrote:

> ??? As for FreeBSD, they could have gone the way of upgrading the
>kernel (I saw some evidences about 10.x but no confirmation yet) but
>depending of their initial work done during the 4.x days, switching
>might have been a better financial choice.

With Junos 15.1, the underlying FreeBSD was upgraded to 10.x - except for
on MX104 (MIPS RE).

As for the silicon, MX, PTX & some QFXs are based on Junipers own ASICs.

--
BR, Sonny

"Respect is fine, but actually I've always wanted to be feared."
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
Once upon a time, Alain Hebert <ahebert@pubnix.net> said:
> ??? I haven't unpackaged an Evolved distribution yet, but my
> experience with WindRiver licensing back in early 2000, it would be
> pricey.

Heh, when you pay 6 figures for a router, two copies of Wind River Linux
for the REs is probably barely a bump. Also, I expect Juniper would be
able to get some volume discounts. After all, there are a number of
free IoT type Linux distributions as well now that give some level of
competition to Wind River (obviously not the same, but probably bring
down the price).

Also, back when "embedded system" meant getting like 4MB RAM and 8MB
flash, it was a lot harder (read: pricier) to get a regular Linux setup
into that. Now that even phones are often coming with 6-8GB RAM and
64-256G flash (and oh yeah, running Linux ;) )... "embedded" isn't quite
the same anymore.

> ??? As for FreeBSD, they could have gone the way of upgrading the
> kernel (I saw some evidences about 10.x but no confirmation yet) but
> depending of their initial work done during the 4.x days, switching
> might have been a better financial choice.

They've upgraded FreeBSD a few times over the years, but each time it
tended to be a "big deal" upgrade (versions you couldn't skip, no
downgrades without a full reload, changed behvaior, etc.).

--
Chris Adams <cma@cmadams.net>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: Junos OS Evolved [ In reply to ]
Data Center use cases, except some PTX10000 products... albeit the ones that are dual personality with their QFX alter ego :-)

Sent from my iPhone

> On Oct 13, 2020, at 3:30 PM, Richard McGovern <rmcgovern@juniper.net> wrote:
>
> ?I am thinking (guessing) you will not see EVO on MX for some time. EVO is mainly targeted at Data Center use cases, for which MX is used for DC to DC connectivity, but not as a main stay within any DC.
>
> My 2 cents worth.
>
> 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/11/20, 6:26 AM, "Saku Ytti" <saku@ytti.fi> wrote:
>
>> On Sun, 11 Oct 2020 at 00:24, Colton Conor <colton.conor@gmail.com> wrote:
>>
>> So is Junos OS Evolved available for the MX routers? How would you go from regular Junos to Junos OS Evolved on a MX 240/480/960 for example?
>
> It is not, but expect to see it in future MX REs.
>
>
>
> --
> ++ytti
>
>
>
> Juniper Business Use Only
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp