Hi Torsten, here are the missing bits:
> "clnode remove" would only be used if the node you want to remove is > still bootable into non-cluster mode. Let's consider the case that it is still bootable. When I try the clnode remove in non-cluster mode, I get this: --- 8< --- Attempting to unconfigure pub2-node0 from the cluster ... failed Please consider the following warnings: scrconf: Failed to remove node (pub2-node0) - node is in use. scrconf: Node "pub2-node0" is still cabled. Node "pub2-node0" is still in use by device group "nfs-dg". Node "pub2-node0" is still in use by quorum device "d1". --- 8< --- After clnode remove, the node is still configured in the cluster: --- 8< --- oot at pub2-node1:~# clnode status === Cluster Nodes === --- Node Status --- Node Name Status --------- ------ pub2-node0 Offline pub2-node1 Online --- 8< --- > I would assume that you need to remove the node from other things like > resource groups, quorum device, etc, before you actually perform the > "clnode clear -F node-b" from node-a (again being in cluster mode). In this case, I have removed the node from all resource groups, but two issues remain: * Removing it from the SVM set (this reason why I started this thread) * Removing it from the quorum device (I have not started looking at this, but I expect more issues) clnode clear also fails due to the "dead" node still being configured in the disk set: --- 8< --- root at pub2-node1:~# clnode clear -F pub2-node0 Oct 14 16:16:59 pub2-node1 genunix: NOTICE: clcomm: Path pub2-node1:xnf3 - pub2-node0:xnf3 has been deleted Oct 14 16:16:59 pub2-node1 genunix: NOTICE: clcomm: Adapter xnf3 has been disabled Oct 14 16:16:59 pub2-node1 genunix: NOTICE: clcomm: Path pub2-node1:xnf2 - pub2-node0:xnf2 has been deleted Oct 14 16:16:59 pub2-node1 genunix: NOTICE: clcomm: Adapter xnf2 has been disabled Oct 14 16:16:59 pub2-node1 ip: ip: joining multicasts failed (18) on clprivnet0 - will use link layer broadcasts for multicast clnode: Cannot remove node "pub2-node0" from SVM device group "nfs-dg". clnode: (C562030) An unexpected error occurred; failed to clear node "pub2-node0". --- 8< --- Thank you, Nils