Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Node unjoin fails in ONTAP with 'Node is SFO and Node still has volumes'

Views:
460
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
core
Last Updated:

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.

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?