Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Node_unjoin_fails_in_ONTAP_with_Node_is_SFO_and_Node_still_has_volumes
      Applies to FAS8020 ONTAP 9.1P3 Issue Failure when trying to unjoin a node while in takeover mode. Node 01 had previously failed and was taken over by node 02. The customer was able to unjoin node 01 w...Applies to FAS8020 ONTAP 9.1P3 Issue Failure when trying to unjoin a node while in takeover mode. Node 01 had previously failed and was taken over by node 02. The customer was able to unjoin node 01 without issue. Executing cluster unjoin -node <node_name> on node 02 would not unjoin due to: Cluster unjoin only works for nodes not in a failover configuration. Node is SFO enabled with partner node . Node has 2 volumes. Please either move or delete them from the node before unjoining.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/LIF_is_operationally_down_after_unjoin_the_node
      iSCSI LIF is down and unable to bring up after node unjoin/rejoin(node replacement) 2020-08-04T08:19:31.722Z cpu13:2314298)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:735: Path "vmhba64:C11:T1:L6" (DO...iSCSI LIF is down and unable to bring up after node unjoin/rejoin(node replacement) 2020-08-04T08:19:31.722Z cpu13:2314298)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:735: Path "vmhba64:C11:T1:L6" (DOWN) command 0xa3 failed with status Timeout. 2020-08-04T08:19:31.722Z cpu13:2314299)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:735: Path "vmhba64:C11:T1:L7" (DOWN) command 0xa3 failed with status Timeout. H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Snapmirror_operations_failing_after_nodes_unjoin_from_cluster
      Applies to ONTAP 9.8P3 SVMDR Issue SnapMirror operation failing with error after nodes unjoin from cluster Error: Failed to get information for node "<NODEUUID>". Reason: entry doesn't exist.
    • https://kb.netapp.com/on-prem/ontap/DM/Encryption/Encryption-KBs/Cannot_remove_node_XX_because_its_storage_encryption_devices_use_authentication_keys
      Applies to Attempts to unjoin a node from cluster fail with error: ::>cluster remove-node -node cluster-01 Command failed, Cannot remove node cluster-01 because its storage encryption devices use auth...Applies to Attempts to unjoin a node from cluster fail with error: ::>cluster remove-node -node cluster-01 Command failed, Cannot remove node cluster-01 because its storage encryption devices use authentication keys that will not be available to the node after it leaves the cluster. Use "storage encryption disk show" and "storage encryption disk modify" commands to set the FIPS and data AKs of the devicesowned by the node and the failover partner to the default manufacturer secure ID keyID 0x0.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Unjoin_nodes_with_one_node_failing_to_power_on
      Applies to ONTAP 9 Issue 1 of 2 nodes that need to be removed from the cluster (unjoined) fails to power on - cannot even reach the LOADER As a result, "cluster remove-node" (unjoin) of the node fails...Applies to ONTAP 9 Issue 1 of 2 nodes that need to be removed from the cluster (unjoined) fails to power on - cannot even reach the LOADER As a result, "cluster remove-node" (unjoin) of the node fails The HA partner node is in takeover mode
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Cluster_remove-node_fails_referencing_MDV_CRS_volume
      Applies to ONTAP 9 Issue Node cannot be unjoined from the cluster due to MDV_CRS volume(s) on the node being removed: Error: command failed: [Job 51523] Job failed: Failed to disable cluster-scoped me...Applies to ONTAP 9 Issue Node cannot be unjoined from the cluster due to MDV_CRS volume(s) on the node being removed: Error: command failed: [Job 51523] Job failed: Failed to disable cluster-scoped metadata volume support prior to remove node operation. Reason: Aggregate "aggr1" cannot be deleted because it contains a system volume named "MDV_CRS_50106aaae75a11e48bad00a09865dcc1_B". This volume must be moved to another aggregate before aggregate "aggr1" can be deleted.