This sounds interesting and I’ve tried that now:
CLUSTER::> version -node *
nodeA :
NetApp Release 9.3P6: Thu Jun 14 20:21:25 UTC 2018
nodeB :
NetApp Release 9.3P6: Thu Jun 14 20:21:25 UTC 2018
2 entries were displayed.
CLUSTER::> cluster image package show
Package Version Package Build Time
---------------- ------------------
9.3P6 6/15/2018 00:21:25
9.5P12 4/10/2020 22:20:31
9.7P11 1/13/2021 03:00:49
3 entries were displayed.
CLUSTER::> cluster image update -version 9.7P11
Starting validation for this update...
It can take several minutes to complete validation...
[… your house will burn, your kids will die …]
Warning: Validation has reported warnings.
Info: The upgrade will happen in two stages.
Stage 1: Cluster will be upgraded to intermediate release (Data ONTAP 9.5P12)
Stage 2: Cluster will be upgraded from Data ONTAP 9.5P12 to Data ONTAP 9.7P11
CLUSTER::> cluster image show-update-progress
Upgrade Stage (1 of 2): Upgrade from 9.3P6 to 9.5P12
Estimated Elapsed
Update Phase Status Duration Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks completed 00:10:00 00:00:28
Data ONTAP updates in-progress 01:17:00 00:00:05
So thanks, learned something new here that will save us some time for multi-hop upgrades
😊
Best,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Toasters <toasters-bounces@teaparty.net>
Im Auftrag von tmac
Gesendet: Donnerstag, 4. März 2021 04:56
An: Brian Parent <bparent@ucsd.edu>
Cc: toasters@teaparty.net
Betreff: Re:
That is correct and wrong at the same time ;)
You still cannot go directly from 9.3 to 9.7. I have heard you can load up 9.5 and 9.7 images and it will progress through:
9.3 -> 9.5 and then 9.5 -> 9.7
Still a double hop, but somewhat automated.
Personally, I would still do the 9.3 -> 9.5, wait at least 24 hours and then do the 9.5 -> 9.7
On Wed, Mar 3, 2021 at 8:44 PM Brian Parent via Toasters <toasters@teaparty.net> wrote:
---------- Forwarded message ----------
From: Brian Parent <bparent@ucsd.edu>
To: Heino Walther <hw@beardmann.dk>
Cc: "toasters@teaparty.net" <toasters@teaparty.net>
Bcc:
Date: Wed, 3 Mar 2021 17:41:48 -0800
Subject: Re:
I'm hearing conflicting information about being limited to 2 versions per hop.
Our support team says once we're at 9.3, we should be able to go directly to 9.7.
I guess we'll find out, and I can update this list on how it goes.
The update is scheduled for late March.
Re:
> From: Heino Walther <hw@beardmann.dk>
> Date: Fri, 5 Feb 2021 19:08:57 +0000
> Subject: SV:
> To: Brian Parent <bparent@ucsd.edu>, "toasters@teaparty.net"
> <toasters@teaparty.net>
>
> I would recommend 9.7p10
>
> Be aware that you can only jump 2 versions… so it’s 9.1 to 9.3 to 9.5 to 9.7 😉
> I would recommend a pause between each version, and get the latest patched version also…
> I seem to remember one specific version where the cluster certificate in the downloaded ontap version was expired, which resulted in an upgrade of the cluster never completing… no downtime or anything, but NetApp support had to fix the cluster database… 😊
>
> I have been working with NetApp for 15 years and never done a real production revert in my life 😉. But maybe I’m just lucky?
>
> /Heino
>
>
> I've got an AFF8020 running 9.1P10 and wondering whether I should target 9.6P10 or 9.7P10 as the destination version.
> I'm aware that such an upgrade will require a hop to 9.3 first.
> I'm also aware that reversion can not skip a release, which is a little scary. I *really* hope I don't have to revert
> from 9.6 or 9.7 all the way back to 9.3 (3 or 4 hops).
>
> What I'm looking for is advice on 9.6p10 vs. 9.7p10. Any horror stories of either release?
> I'm leaning towards 9.7p10, just because it's more recent.
>
>
> Fra: Toasters <toasters-bounces@teaparty.net> på vegne af Brian Parent via Toasters <toasters@teaparty.net>
> Dato: fredag, 5. februar 2021 kl. 19.22
> Til: toasters@teaparty.net <toasters@teaparty.net>
> Emne: <no subject>
> _______________________________________________
> Toasters mailing list
> Toasters@teaparty.net
> https://urldefense.com/v3/__https://www.teaparty.net/mailman/listinfo/toasters__;!!Mih3wA!QxORDgWRDHzpMqq8n1se9Qyhg0knsLVaxgXy6W8O4nYcjoHvQMp0ckrekdY6qvU$
--
Brian Parent
Information Technology Services Department
ITS Computing Infrastructure Operations Group
its-ci-ops-help@ucsd.edu (team email address for Service Now)
UC San Diego
(858) 534-6090
---------- Forwarded message ----------
From: Brian Parent via Toasters <toasters@teaparty.net>
To: Heino Walther <hw@beardmann.dk>
Cc: "toasters@teaparty.net" <toasters@teaparty.net>
Bcc:
Date: Thu, 4 Mar 2021 01:42:00 GMT
Subject:
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
https://www.teaparty.net/mailman/listinfo/toasters