You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@MrObvious thank you for your feedback. Could you provide a bit more clarity? Do you mean the current ONTAP version might not be compatible for a direct upgrade to the target ONTAP version? The upgrade paths cover how a customer gets from any version of ONTAP 9 to any other version. Or do you mean the current hardware might not support the target ONTAP version? The topic in question advises the user to check HWU to confirm that the hardware platform is supported in the target ONTAP release. I'm not sure how to access the case for additional details. Thank you.
Your hardware platform, cluster management switches and MetroCluster IP switches must support the target release. If your cluster is configured for SAN, the SAN configuration must be fully supported."
If a customer is looking to upgrade an older system that cannot go past a certain release, I just think we could add some verbiage to cover this use case. Is that possible?
@MrObvious I think what you want to point out is the following:
NOTE: The version of ONTAP that you can upgrade to might be limited based upon your hardware configuration. If your hardware doesn't support the version of ONTAP software that you want to upgrade to, will to first add new nodes to your cluster, migrate your data, remove the older nodes and then upgrade your ONTAP software. Follow the procedure to Add new nodes to an ONTAP cluster.
Page URL
https://docs.netapp.com/us-en/ontap/upgrade/confirm-configuration.html
Page title
Confirm ONTAP support for your hardware configuration
Summary
https://docs.netapp.com/us-en/ontap/upgrade/prepare.html step 4 links to this, and it is a slight gap that it doesn't say explicitly that ONTAP versions may not be compatible. For example, please see case 2009927286.
Thanks,
Paul
Public issues must not contain sensitive information
The text was updated successfully, but these errors were encountered: