NetApp Cluster-Mode Takeover of epsilon node

If you attempt a manual takeover of a node marked as epsilon, you will receive the following warning:

warning: Takeover of the node holding epsilon can result in data serving failure of the entire cluster. Should an additional node go out of service while the node holding epsilon is out of service, a cluster-wide data serving failure will cause client disruption.

This isn't as scary as it seems...it's important to do correctly, but it's also easy.  To change the node marked as epsilon, do the following:

Change to advanced privilege level:

cluster::> set -privilege advanced

Change to advanced privilege level:

cluster::*> cluster show -epsilon * 

Node            Health  Eligibility   Epsilon
--------------- ------- ------------  ------------
node-01         true    true          false
node-02         true    true          false
node-03         true    true          false
node-04         true    true          true

4 entries were displayed.

Next, mark the current node as false
cluster::*> cluster modify -epsilon false -node CURRENTNODE  

Lastly, mark the new node as true
cluster::*> cluster modify -epsilon true -node NEWNODE

Verify that the change worked:

cluster::*> cluster show -epsilon * 

Node            Health  Eligibility   Epsilon
--------------- ------- ------------  ------------
node-01         true    true          false
node-02         true    true          false
node-03         true    true          true
node-04         true    true          false

4 entries were displayed.

After this, you should be able to take over the node previously holding the epsilon.