Re: Upgrade thoughts: 8.3 -> 9.1 -> 9.3

Douglas Siggins <[email protected]>
Newsgroups gmane.comp.hardware.netapp
Message-ID <CAPJgcAT1TVyvHBbStzpEw-FHvxcQeMjpF45gYj=o4OxSrmoXHQ@mail.gmail.com>
John,
Did you have a look at fastpath?
https://whyistheinternetbroken.wordpress.com/2018/02/16/ipfastpath-ontap92/
It seems every time we put in a case for upgrades to 9.3 netapp support
tries to make sure we looked into this! So it must've bitten a lot of folks.

We did run into a pretty big bug on the upgrade from 9.1 to 9.3P15 -- we
have a case/core in now. I've seen nfs stop serving from a node in at least
3 clusters roughly a 2-5 hours after the upgrade. We fix it by indicating
the unresponsive node and either powering it down, or via NMI/SP. It will
not respond to normal takeover commands. Preliminary core analysis (no full
core analysis yet) points at at least 1 bug fixed in 9.3P17.

https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1236722


Typically when we roll updates it can take months given the number of nodes
and clusters. So we stick with whatever P patch we rolled on the first set
of nodes, and then by the end of upgrades 1-3 P patches are released.

With this experience, always use the latest P patch possible on the
intermediary update especially if you are going to take a bit to roll it
through your entire deployment. I also recommend taking a look at going to
9.5, it sounds nuts, but we've had better stability with this release. We
move to this release because of a specific feature that was needed
(CIFS/SMB enhancements, and flexcache/flexgroups).

Regards,
Douglas


On Tue, Mar 3, 2020 at 4:41 PM John Stoffel <[email protected]> wrote:

>
> Guys,
>
> We're getting ready to ugprade our 4 node 8060 cluster from 8.3.2P9 to
> 9.1P19 and then onto 9.3P17, all this weekend.  My only real concern
> is the upgrade from 9.1 to 9.3, which lists a major warning for bug
> 1250500:
>
>   Expired truststore security certificates causing upgrade and
>   new installation failures.
>
> Unfortunately, I can't run an upgrade advisor report for my cluster
> going from 9.1P19 to 9.3P17, because I'm not yet running 9.1, and it
> can take upto a week for the autosupport data to get pushed to Upgrade
> Advisor.  Sigh...
>
> Has anyone run into this issue when doing the 9.1 -> 9.3 upgrade with
> the expired certificate?  Otherwise, it all looks good, my cluster
> switches are supported at their current version, etc.
>
> John
> _______________________________________________
> Toasters mailing list
> [email protected]
> http://www.teaparty.net/mailman/listinfo/toasters
>

_______________________________________________
Toasters mailing list
[email protected]
http://www.teaparty.net/mailman/listinfo/toasters
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.