Removing clustering

Enter the following command on either node console, as shown in the following example:

cf disable

Disable the cluster license using the following command, as shown in the following example:

license delete cluster

Note
If you are using a version of Data ONTAP earlier than 6.4, the command is license cluster=disable.

Open the /etc/rc file with a text editor and remove references to the partner node in the ifconfig entries, as shown in the following example:

Original entry:

ifconfig e0 199.9.204.254 partner 199.9.204.255

Edited entry:

ifconfig e0 199.9.204.254

Repeat Steps 1 through 3 on the partner node.

Go to Removing clustering hardware.

Halt both nodes by entering the following command on each console:

halt

Turn off the power to each node, then turn off the power to the disk shelves and unplug them from the power source.

Ground yourself, then remove the cluster interconnect cables from both nodes.

In a FAS940 or FAS960, open both nodes and remove the cluster adapters, and then close the nodes.

In a FAS980, if a regular cluster is being converted to a stand-alone filer, the NVRAM5 adapter must be removed from slot 11 and installed in slot 10. If a metrocluster is being converted to a stand- alone filer, the VI cluster adapter must be removed from slot 11.

See the Hardware and Service Guide for additional information.

Unplug the local node from the partner node's Channel B disk shelf and do the same for the partner node.

If you are converting to a...

Then...

System with nonmirrored disks

1. Disconnect all cabling from the Channel B loop on the local node.
2. Repeat Step 1 for the partner node.

System with mirrored disks or redundant Channel B loop

1. Connect the local node to the open Channel B loop in its local disk shelves, as described in the appropriate disk shelf guide.
2. Repeat Step 1 for the partner node.

Power on the disk shelves, then the individual nodes, monitoring the system console for error messages during the boot process.

Run all system diagnostics at the boot prompt by entering the following command on the system console:

sysdiag

Unset the partner sysid by entering the following command at the prompt:

unsetenv partner-sysid

Boot the node by entering the following command:

boot

Check clustering status by entering the following command:

cf status

Result

If clustering is disabled, you see the following output:

Cluster monitor not initialized

Repeat Step 1 through Step 11 for the partner node.