Check to see the current status of cNFS:
[root@foonsd1 ~]# mmlscluster --cnfs GPFS cluster information ======================== GPFS cluster name: fooamcp.example.org GPFS cluster id: 10159024612008204251 Cluster NFS global parameters ----------------------------- Shared root directory: /net/foodata1/cnfsSharedRoot Virtual IP address: foonfs.example.org rpc.mountd port number: 892 nfsd threads: 128 Reboot on failure enabled: yes CNFS monitor enabled: yes Node Daemon node name IP address CNFS state group CNFS IP address list ------------------------------------------------------------------------------------------- 16 foonsd1.example.org 140.252.27.15 enabled 0 140.252.27.10,140.252.27.12 17 foonsd2.example.org 140.252.27.16 disabled 0 140.252.27.11,140.252.27.13
We can either just disable the one active cNFS node like this:
[root@foonsd1 ~]# mmchnode --cnfs-disable -N foonsd1,foonsd2 Mon Mar 25 17:16:15 MST 2013: mmchnode: Processing node foonsd1.example.org Mon Mar 25 17:16:15 MST 2013: mmchnode: Processing node foonsd2.example.org mmchnode: Propagating the cluster configuration data to all affected nodes. This is an asynchronous process.
Or disable cNFS permanently but deleting it’s configuration. Note that when your permanently removing the cNFS configuration it’s not necessary to first disabled it.
[root@foonsd1 ~]# mmchnode --cnfs-interface=DELETE -N foonsd1,foonsd2 Mon Mar 25 17:16:43 MST 2013: mmchnode: Processing node foonsd1.example.org Mon Mar 25 17:16:43 MST 2013: mmchnode: Processing node foonsd2.example.org mmchnode: Propagating the cluster configuration data to all affected nodes. This is an asynchronous process.
Verifying that cNFS is now disabled:
[root@foonsd1 ~]# mmlscluster --cnfs GPFS cluster information ======================== GPFS cluster name: fooamcp.example.org GPFS cluster id: 10159024612008204251 mmlscluster: CNFS is not defined in this cluster.