This is not applicable to MX80 (as platform was mentioned by topic starter).
On 12-Mar-19 15:38, adamv0...@netconsultings.com wrote:
Upgrading from 12.3 to 15.1 upgrades the FreeBSD version from 6.1 to
10.0.
Upgrading from 12.3xxx to 15.1xxx reformats the file system. Only specific
fil
> Saku Ytti
> Sent: Sunday, March 10, 2019 2:49 PM
>
> On Sun, Mar 10, 2019 at 4:30 PM Tom Beecher
> wrote:
>
> > was when it was shut down. ( Hopefully. :) ) When you upgrade it, the
> > process only modifies certain components. Any OS upgrade process like
> > that
>
> This is not true, the up
On Sun, Mar 10, 2019 at 4:30 PM Tom Beecher wrote:
> was when it was shut down. ( Hopefully. :) ) When you upgrade it, the
> process only modifies certain components. Any OS upgrade process like that
This is not true, the upgrade is fresh install. It is not like you do
upgrade on your laptop Fre
This was, and still is, the most accurate answer in the thread. To expand
on it further
Cisco IOS images are standalone binary images. Each time the device is
powered on, it loads the image it is configured too, and executes it. The
entire operating system is encapsulated in this image file, a
On 9/Mar/19 11:18, Saku Ytti wrote:
> So Gert's question 'y tho?' is very much valid, and the most obvious
> reasons is because Juniper doesn't want to increase the product cost
> to cover lab testing from any-to-any, as it would mean ever increase
> money and time cost to release. By setting s
Hi,
On Sat, Mar 09, 2019 at 11:18:35AM +0200, Saku Ytti wrote:
> b) The installation is success, but platform doesn't come up configured right:
> - Because IOS accepts config unatomically line-by-line, you can
> give it arbitrarily bad config, and it'll eat what it can, making it
> robust betw
Hi,
On Sat, Mar 09, 2019 at 07:07:49AM +0200, Mark Tinka wrote:
> With Junos being based on FreeBSD, you can see why this makes sense.
Not really :-)
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come ou
On Sat, Mar 9, 2019 at 7:11 AM Mark Tinka wrote:
> Just as with FreeBSD (if you've used it before), you can upgrade to 11
> if you are coming from 9.3 and any official version of 10. For anything
> earlier than that, you'd need to upgrade to 10 first.
I don't think this is it. Junos is lot more
On 8/Mar/19 23:12, Gert Doering wrote:
> So?
Just as with FreeBSD (if you've used it before), you can upgrade to 11
if you are coming from 9.3 and any official version of 10. For anything
earlier than that, you'd need to upgrade to 10 first.
You can upgrade to 10 if you are coming from any off
On 8/Mar/19 16:56, Pierre Emeriaud wrote:
>
> As others said, direct upgrade is somewhat unsupported and quite bold.
>
> We're currently upgrading mx480s from 13.3R5 to 17.2R2 with an
> intermediate step on 15.1F5. As those are LNSes we have to activate
> tomcat (`services subscriber-management
My point is only that they made a _lot_ of changes to the underlaying
systems between 12/13/14 and 15 (as far as I understand it 15 is
basically forked from 12, so changes done in 13 and 14 are not
necessarily in 15). But they still changed a lot, especially the whole
change from running as a
Lately, we have been upgrading lots of our ACX5048's from 15.1X54 (D51 and
D61) to 17.3R3.10
-Aaron
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Hi,
> On Fri, Mar 08, 2019 at 01:17:44PM -0700, Eldon Koyle wrote:
>> Many (most?) network operating systems are an image file that the
>> switch either writes over a partition (ie. block-level copy) or boots
>> directly (ie. initrd/initramfs) with a separate partition for a config
>> file. Junos
Hi,
On Fri, Mar 08, 2019 at 01:17:44PM -0700, Eldon Koyle wrote:
> Many (most?) network operating systems are an image file that the
> switch either writes over a partition (ie. block-level copy) or boots
> directly (ie. initrd/initramfs) with a separate partition for a config
> file. Junos is a
Many (most?) network operating systems are an image file that the
switch either writes over a partition (ie. block-level copy) or boots
directly (ie. initrd/initramfs) with a separate partition for a config
file. Junos is a full BSD operating system that installs packages to
partitions on the devi
Hi,
On Fri, Mar 08, 2019 at 10:38:16AM +0100, "Rolf Hanßen" wrote:
> usually they say not more than 2 major releases in one step (i.e. 13 -> 15
> -> 17).
So why is that?
Genuinely curious, as I do not have much JunOS upgrade experience - and
my Cisco IOS experience so far has been "you can go fr
Le ven. 8 mars 2019 à 10:26, Robert Hass a écrit :
>
> Hi
> Can I do direct upgrade of JunOS 13.2S to 17.4S ?
> Platform is MX80
> Or should I go step by step: i.e:
> 13.2 -> 14.1
> 14.1 -> 15.1
> 15.1 -> 16.1
> 16.1 -> 17.1
> 17.1 -> 17.4
As others said, direct upgrade is somewhat unsupported an
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Ola
Thoresen
Sent: 08 March 2019 09:41
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Old JunOS upgrade path
Not that I am in any way authoritative... And I think Juniper has official
guidelines, but these might be a bit conservative
Not that I am in any way authoritative... And I think Juniper has
official guidelines, but these might be a bit conservative. Depending on
your config and feature sets.
But I would at least suggest doing a few steps.
13.2 to 15.1 should be ok - skipping 14.
15.1 to 17.1 (and probably even 17
Hi,
usually they say not more than 2 major releases in one step (i.e. 13 -> 15
-> 17).
kind regards
Rolf
> Hi
> Can I do direct upgrade of JunOS 13.2S to 17.4S ?
> Platform is MX80
> Or should I go step by step: i.e:
> 13.2 -> 14.1
> 14.1 -> 15.1
> 15.1 -> 16.1
> 16.1 -> 17.1
> 17.1 -> 17.4
>
>
Hi
Can I do direct upgrade of JunOS 13.2S to 17.4S ?
Platform is MX80
Or should I go step by step: i.e:
13.2 -> 14.1
14.1 -> 15.1
15.1 -> 16.1
16.1 -> 17.1
17.1 -> 17.4
Rob
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/
21 matches
Mail list logo
