Search

How to perform Manual Ontap Upgrade while incorporating the monitoring actions recommended to mitigate the impact to any SAN hosts losing access to ONTAP LUNs
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_perform_Manual_Ontap_Upgrade_while_incorporating_the_monitoring_actions_recommended_to_mitigate_the_impact_to_any_SAN_hosts_losing_access_to_ONTAP_LUNs
Applies to Ontap 9 Manual Ontap Upgrade Description Recommended upgrade plan to incorporate the monitoring actions recommended to mitigate impact to any SAN hosts losing access to ONTAP LUNs, if there...Applies to Ontap 9 Manual Ontap Upgrade Description Recommended upgrade plan to incorporate the monitoring actions recommended to mitigate impact to any SAN hosts losing access to ONTAP LUNs, if there are CRC errors on any cluster port during upgrades.
Upgrade was paused due to Node not in connected state after giveback
https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Upgrade_was_paused_due_to_Node_not_in_connected_state_after_giveback
Thu Aug 22 18:42:39 +1000 [Node1: upgrademgr: upgrademgr.update.pausedErr:error]: The automated update of the cluster has been paused due to the following reason: Node "Node1": Error: {Node "Node2" is...Thu Aug 22 18:42:39 +1000 [Node1: upgrademgr: upgrademgr.update.pausedErr:error]: The automated update of the cluster has been paused due to the following reason: Node "Node1": Error: {Node "Node2" is not in "connected" state after giveback.}, Action: {Use the "storage failover show" command to verify that node "Node2" is in the "connected" state.}.