When upgrading OnTap minor release versions (P1 -> P5), the following cmdlet works as expected:
Invoke-NcClusterHaTakeover -Controller $connectedController -Node $controllerBNode
When upgrading OnTap major release versions (9.2 -> 9.3), the following cmdlet produces the following error message:
Failed to initiate takeover. Reason: version mismatch. Note: If you are performing a Data ONTAP non-disruptive upgrade or downgrade, use the (privilege: advanced) "-option allow-version-mismatch" parameter.
This is all well and good and so I add AllowVersionMismatch switch parameter as follows:
Invoke-NcClusterHaTakeover -Controller $connectedController -Node $controllerBNode -AllowVersionMismatch
But receive the same error message:
Failed to initiate takeover. Reason: version mismatch. Note: If you are performing a Data ONTAP non-disruptive upgrade or downgrade, use the (privilege: advanced) "-option allow-version-mismatch" parameter.
I'm hoping it is obvious what I missing and/or how I elevate to "set -privilege advanced" from the Netapp Powershell CLI. I have considered performing this takeover step with Invoke-NcSSH, but I am hoping there is a more elegant way and that I am just missing a step or something obvious. (Invoke-NcSsh option mentioned here: https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Do-we-have-any-DataONTAP-powershell-toolkit-cmdlet-to-set-privilege-level-for/td-p/116795)
The parameter help talks about cleanly halting the node to be taken over but this doesn't quite make sense to me - is it a clue to someone else? I am not familiar with proatively halting a node during a NDU:
-AllowVersionMismatch
If specified, allow takeover if the partner was running an incompatible operating system version and was cleanly halted. This option is used for non-disruptive upgrade (NDU).Thanks in advance for your insight!