[j-nsp] mx960 junos upgrade fail

[Aaron Gould]

mx960 junos upgrade fail due to the following reasons. any idea how to
overcome?





I already did request system storage cleanup





{master}

***@mx960> show version invoke-on all-routing-engines | grep
"Model|Junos:"

Model: mx960

Junos: 15.1F7.3

Model: mx960

Junos: 15.1F7.3





{master}

***@mx960> request system software validate in-service-upgrade
junos-install-mx-x86-64-16.1R3-S7.1.tgz

error: Not enough free_space: 17770832 reqd_pkgsize: 18181496

error: not enough space in /var on re0.

error: need at least 9308927696 bytes free.









- Aaron

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Brian Nelson]

My notes for upgrade from 15.1F# to 16.1 state ISSU not supported to
that release level of 16.1. Can't find the exact reference; but it was
way down in a detailed note on support for the various MPCs.

15.1F# is a non-supported, at your own risk release anyway.

Brian

Post by Aaron Gould
mx960 junos upgrade fail due to the following reasons. any idea how to
overcome?
I already did request system storage cleanup
{master}
"Model|Junos:"
Model: mx960
Junos: 15.1F7.3
Model: mx960
Junos: 15.1F7.3
{master}
junos-install-mx-x86-64-16.1R3-S7.1.tgz
error: Not enough free_space: 17770832 reqd_pkgsize: 18181496
error: not enough space in /var on re0.
error: need at least 9308927696 bytes free.
- Aaron
_______________________________________________
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Nelson, Brian]

(bugging me) Found it, release notes for 16.1R2
: ISSU is not supported from 15.1R releases to 16.1R releases, if ...
multiple sections with all sorts of hardware limitations for ISSU.

I'm waiting on 16.1 or will upgrade during a major outage window.
Brian

-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-***@puck.nether.net] On Behalf Of Brian Nelson
Sent: Thursday, April 05, 2018 10:41 AM
To: Aaron Gould <***@gvtc.com>; juniper-***@puck.nether.net
Subject: Re: [j-nsp] mx960 junos upgrade fail

My notes for upgrade from 15.1F# to 16.1 state ISSU not supported to that release level of 16.1. Can't find the exact reference; but it was way down in a detailed note on support for the various MPCs.

15.1F# is a non-supported, at your own risk release anyway.

Brian

Post by Aaron Gould
mx960 junos upgrade fail due to the following reasons. any idea how to
overcome?
I already did request system storage cleanup
{master}
"Model|Junos:"
Model: mx960
Junos: 15.1F7.3
Model: mx960
Junos: 15.1F7.3
{master}
junos-install-mx-x86-64-16.1R3-S7.1.tgz
error: Not enough free_space: 17770832 reqd_pkgsize: 18181496
error: not enough space in /var on re0.
error: need at least 9308927696 bytes free.
- Aaron
_______________________________________________
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Aaron Gould]

Thanks Brian, you mentioned issu not supported from 15.1R to 16.1R, but I'm
not doing that... I'm going from 15.1F to 16.1R

- Aaron


_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Aaron Gould]

When I ftp'd the file to the MX960, it puts it in /var/home/remote/

When I run the software upgrade command it seems to copy that junos tgz file
to /var/tmp/

....and then tells me I'm out of space. :|

I tried this...

I deleted that junos file from /var/home/remote/

...then specified the new location of where it was auto-copied to during the
upgrade process.... and it now gets past the "Not enough free space" issue,
BUT, now hits up with all sort of other problems.

I see that there are some ISSU unsupported items... wondering why my
MPC7E-MRATE modules are being seen as non-ISSU supported

***@mx960> show chassis hardware models | grep FPC
FPC 0 REV 43 750-056519 (removed) MPC7E-MRATE
FPC 11 REV 43 750-056519 (removed) MPC7E-MRATE

...then the vmhost is seen as too old ... wonder what that is all about ?

Is it to much to jump from 15.1F7.3 to 16.1R3-S7 ? ...maybe I need an
intermediate step in order to get to my end junos version goal? Or is there
perhaps a different vmhost software piece that needs to be upgraded?

I'll ask jtac too.

***@mx960> request system software validate in-service-upgrade
/var/tmp/junos-install-mx-x86-64-16.1R3-S7.1.tgz
FPC 0 will be offlined (In-Service-Upgrade not supported)
FPC 11 will be offlined (In-Service-Upgrade not supported)
PIC 0/0 will be offlined (In-Service-Upgrade not supported)
PIC 11/0 will be offlined (In-Service-Upgrade not supported)
PIC 0/1 will be offlined (In-Service-Upgrade not supported)
PIC 11/1 will be offlined (In-Service-Upgrade not supported)
Verified junos-install-mx-x86-64-16.1R3-S7.1 signed by
PackageProductionEc_2018 method ECDSA256+SHA256
Verified manifest signed by PackageProductionEc_2018 method ECDSA256+SHA256
Checking PIC combinations
Checking vmhost version compatibility
VMHost version too old for Junos
ERROR: package junos-x86-64-16.1R3-S7.1 fails requirements


- Aaron

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Olivier Benghozi]

https://www.juniper.net/documentation/en_US/junos/topics/concept/installation_upgrade.html <https://www.juniper.net/documentation/en_US/junos/topics/concept/installation_upgrade.html>

« Host upgrade—Use the junos-vmhost-install-x.tgz image upgrade. When you upgrade the host OS, you must specify the regular package in the request vmhost software add command. This is the recommended mode of upgrade because this method installs the host image along with the compatible Junos OS. »


By the way, why one would want to updade to 16.1R3S* whereas 16.1R6S2 is available ?

Post by Aaron Gould
...then the vmhost is seen as too old ... wonder what that is all about ?
Checking vmhost version compatibility
VMHost version too old for Junos
ERROR: package junos-x86-64-16.1R3-S7.1 fails requirements

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https

[Aaron Gould]

Resending garbled-output...


***@blcn-960> request system software validate in-service-upgrade
/var/tmp/junos-install-mx-x86-64-16.1R3-S7.1.tgz

FPC 0 will be offlined (In-Service-Upgrade not supported)

FPC 11 will be offlined (In-Service-Upgrade not supported)

PIC 0/0 will be offlined (In-Service-Upgrade not supported)

PIC 11/0 will be offlined (In-Service-Upgrade not supported)

PIC 0/1 will be offlined (In-Service-Upgrade not supported)

PIC 11/1 will be offlined (In-Service-Upgrade not supported)

Verified junos-install-mx-x86-64-16.1R3-S7.1 signed by
PackageProductionEc_2018 method ECDSA256+SHA256

Verified manifest signed by PackageProductionEc_2018 method ECDSA256+SHA256

Checking PIC combinations

Checking vmhost version compatibility

VMHost version too old for Junos

ERROR: package junos-x86-64-16.1R3-S7.1 fails requirements




-Aaron

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Alexander Dube]

Hi Aaron,

did you checked how much space is left on /var/?

show system storage

On my box /var is about 10G

show system storage | grep "File|var"

Filesystem Size Used Avail Capacity Mounted on
/dev/gpt/var 14G 2.8G 10G 22% /.mount/var

ISSU seams to be supported for MPC7E-MRATE as of 17.4R1: https://www.juniper.net/documentation/en_US/release-independent/junos/topics/reference/general/mpc-mx-series-mpc7e-features.html


Regards
Alex
_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Aaron Gould]

Thanks, yes I check space of /var/ and I didn't have enough space, then I deleted one of the copies of the junos tgz file , from /var/home/remote and the issu upgrade process runs, but now I have a vmhost incompatible issue. (oliver suggested something)

I like the idea of being able to do a software upgrade in-service, so I might go ahead and skip 16.1R3-S7 and go with MPC7E issu capable version 17.4R1 This is a brand new 100 gig ring of (5) MX960's that are not in production yet... so now is the time for me to decide the starting junos version, etc.

Btw, as a side-note, I do not have the free space issue, if I do software upgrade without issu option.... space issue is only when I use ....in-service-upgrade

Oliver, you mentioned "By the way, why one would want to updade to 16.1R3S* whereas 16.1R6S2 is available" ...but I'm actually trying to upgrade to 16.1R3-S7 ...however, now alex had informed me that my MPC7E modules aren't issu capable until 17.4R1, so I might go ahead with that version instead.

Oliver, I was trying to use a file from juniper titled "64 Bit-MX High-End Series" but are you telling me that I should be using one of the files titled " VMHost 64-Bit" ?

Also, what is the difference in " VMHost 64-Bit" and "VMHost Net 64-Bit" ?


Install Package Checksum Release Format Size File Date

64 Bit-MX High-End Series MD5 SHA1 SHA2 17.4R1-S2 tgz 2,700,607,604 22 Mar 2018

VMHost 64-Bit MD5 SHA1 SHA2 17.4R1-S2 tgz 2,367,498,414 22 Mar 2018

VMHost Net 64-Bit MD5 SHA1 SHA2 17.4R1-S2 tgz 2,413,867,390 22 Mar 2018

Thanks everyone, y'all are awesome!

-Aaron

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[Olivier Benghozi]

Not sure you really can ISSU update between such versions...

About the OS file, you want vmhost 64bits.
The Net version is to freshinstall using PXE Netboot.

And the "64 Bit-MX High-End Series" is the one you would use with a RE-1800 (directly running JunOS over FreeBSD over its hardware), while you have a more recent one (like RE-MX-Xsomething), running JunOS over FreeBSD over KVM over Linux. In your case, this image can update only the JunOS+FreeBSD within the KVM, but it won't update the Linux/KVM stuff (named "vmhost").
https://www.juniper.net/documentation/en_US/junos/topics/concept/re-mx-x6-x8-ptx-x8-overview.html <https://www.juniper.net/documentation/en_US/junos/topics/concept/re-mx-x6-x8-ptx-x8-overview.html>

Post by Aaron Gould
I like the idea of being able to do a software upgrade in-service, so I might go ahead and skip 16.1R3-S7 and go with MPC7E issu capable version 17.4R1 This is a brand new 100 gig ring of (5) MX960's that are not in production yet... so now is the time for me to decide the starting junos version, etc.
Btw, as a side-note, I do not have the free space issue, if I do software upgrade without issu option.... space issue is only when I use ....in-service-upgrade
Oliver, you mentioned "By the way, why one would want to updade to 16.1R3S* whereas 16.1R6S2 is available" ...but I'm actually trying to upgrade to 16.1R3-S7 ...however, now alex had informed me that my MPC7E modules aren't issu capable until 17.4R1, so I might go ahead with that version instead.
Oliver, I was trying to use a file from juniper titled "64 Bit-MX High-End Series" but are you telling me that I should be using one of the files titled " VMHost 64-Bit" ?
Also, what is the difference in " VMHost 64-Bit" and "VMHost Net 64-Bit" ?

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.

[Wojciech Janiszewski]

I'd first check if /var is mounted on the hard drive.

Regards,
Wojciech

Post by Aaron Gould
mx960 junos upgrade fail due to the following reasons. any idea how to
overcome?
I already did request system storage cleanup
{master}
"Model|Junos:"
Model: mx960
Junos: 15.1F7.3
Model: mx960
Junos: 15.1F7.3
{master}
junos-install-mx-x86-64-16.1R3-S7.1.tgz
error: Not enough free_space: 17770832 reqd_pkgsize: 18181496
error: not enough space in /var on re0.
error: need at least 9308927696 bytes free.
- Aaron
_______________________________________________
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mai