It _is_ supported to _run_ a cluster with a mixed version state for a limited time. (NDO upgrade) No secret flags necessary.
I's a different thing to allow "new" nodes to _join_ the cluster and bring it into a mixed state....
my 2c
On 17/11/27 8:28 PM, Alexander Griesser wrote:
Offtopic here, but if it is not supported to run clusters in a mixed state with 9.3, how would you update a 4 node cluster then?
Will the shiny `cluster image update` wizard automagically take care of the secret flags then or will it update one node per HA pair simultaneously?
Best,
*Alexander Griesser*
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.com mailto:AGriesser@anexia-it.com
Web: http://www.anexia-it.com http://www.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-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] *Im Auftrag von *Konnerth, Karl *Gesendet:* Montag, 27. November 2017 20:05 *An:* tmac tmacmd@gmail.com; Jan-Pieter Cornet johnpc@xs4all.nl *Cc:* Toasters@teaparty.net *Betreff:* RE: Chicken/egg dillema doing a hardware upgrade on a FAS3250
Hi,
It is possible to temporarily have a cluster with mixed versions such as 9.1 with 9.2. You should check with Support about your specific combination, and the capabilities you need to complete the transition (like moving the SnapMirror targets).
This is from the 9.1 Upgrade Express Guide:
*Mixed version requirements*
ONTAP clusters can operate for a limited time in a mixed version state, in which HA pairs in a
cluster are running ONTAP versions from different releases. However, the upgrade is not complete
until all HA pairs are running the new target release. When the cluster is in a mixed version state, you
should not enter any commands that alter the cluster operation or configuration except as necessary to
satisfy the upgrade requirements.
You should complete the upgrade as quickly as possible; do not allow the cluster to remain in a
mixed version state longer than necessary. An HA pair must not run an ONTAP version from a
release that is different from other HA pairs in the cluster for more than seven days.
Beginning 9.3 this is not supported by default, but there is an advanced privilege command to allow mixed versions.
Regards,
---Karl
*From:*toasters-bounces@teaparty.net mailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] *On Behalf Of *tmac *Sent:* Monday, November 27, 2017 8:03 AM *To:* Jan-Pieter Cornet <johnpc@xs4all.nl mailto:johnpc@xs4all.nl> *Cc:* Toasters@teaparty.net mailto:Toasters@teaparty.net *Subject:* Re: Chicken/egg dillema doing a hardware upgrade on a FAS3250
here is an idea...not necessarily supported, but an idea:
Install 9.2P1 on your FAS8200 controllers.
Initialize them with the Root-Data Partitioning
Here is the not necessarily supported part:
- If you do not have a CN1610 or supported stand-alone cluster swithces
-> temporarily utilize a 10-gig switch and convert the 3250 from switchless to switched.
- I think you might be able to add the FAS8200s into the cluster,
they will operate like 9.1 controllers.
If they get moved in, you can then vol move the snapmirror volumes in
After they are all moved, remove the FAS3250 nodes from the cluster
Convert the switched cluster back to a switchless cluster.
again: This process is probably NOT SUPPORTED, but if you are in a pinch, it may work.
It might be worth opening a case to see if you can temporarily add 9.2 to a 9.1 cluster.
--tmac
*Tim McCarthy, */Principal Consultant/
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at **TMACsRack https://tmacsrack.wordpress.com/*
On Mon, Nov 27, 2017 at 10:46 AM, Jan-Pieter Cornet <johnpc@xs4all.nl mailto:johnpc@xs4all.nl> wrote:
We have a FAS3250 that's primarily backup storage. It hosts a lot of snapmirror targets, and a few mounted filesystems with backup data. As the hardware is getting old, we've purchased a shiny new FAS8200 with a couple of 8TB drive shelves. We assume that the FAS8200 can be initialized on 9.2 and above using the ADP on external drives feature, to partition those 8T disks, so we don't have to throw away about 50T of storage just on the root aggregates. However... the FAS3250 hardware can only run ontap 9.1. Newer versions of ontap are not available on that hardware. And to make the 8200 nodes join the existing cluster, it has to run the same sofware version (9.1), so... it cannot be initialized with ADP. And you can't initialize first and partition later, because repartitioning wipes all existing data. That's our dilemma. I've actually tried to "manually" partition the disks, by going into maintenance mode and using "disk partition" to force the 8200 nodes to see only partitioned disks, and then re-initializing them using boot menu "4 - clean config and reinitialize disks". That fails, and 9.1 doesn't want to write a root FS to partitioned disks (it does wipe them, though). Besides, it would likely be unsupported. I did learn some interesting things about the "disk partition" command, by the way, like the "-b" blocksize is in 4k blocks, and the '-i' option that numbers partitions starts at 1, which is a data partition, and number 2 is the root partition, at least in the 2-partition root/data setup. So we either have the option to throw away a large chunk of storage for root aggregates, initialize the new nodes on 9.1, join in cluster, and move the existing data using 'vol move' and all the cDOT goodness that comes with it. ... or build the new 8200 as a separate cluster, initialize it with 9.3, partition the disks via the boot menu, and then move the data over using snapmirror, and remounting the clients. That's doable because most of the data is snapmirror target anyway, and there's a limited number of mounted filesystems that would need a remount. It's a shame that cDOT doesn't have "snapmirror migrate" like 7mode did. Does anyone have any other options? All I could think is get swing gear and basically do the migration twice, first to hardware that supports ontap >= 9.2, then to our new 8200. But I'm not willing to spend a lot of money renting the swing gear and getting a lot of extra setup work basically because of a flaw in netapp software. Thanks, -- Jan-Pieter Cornet <johnpc@xs4all.nl <mailto:johnpc@xs4all.nl>> "Any sufficiently advanced incompetence is indistinguishable from malice." - Grey's Law _______________________________________________ Toasters mailing list Toasters@teaparty.net <mailto:Toasters@teaparty.net> http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters