Enable NFSv4 with NFS-HA
Disable a Clustered NFS
In a configuration with a single VIP, the NFS-HA is disabled by default and the only options is Active backup NFSv4 only HA.
In a scale-out configuration, the NFSv3 is enabled by default. If you need to disable NFS-HA, run the following command:
Active Backup NFSv4 Only HA
Active backup NFSv4 HA is only available in a single VIP configuration; in this case, the NAS cluster master node provides the NFSv4 services.
The client must mount the master VIP address.
Note: By default, NFS-HA is disabled in a cluster configuration with a single VIP; you must enable it to use the feature.
Do the following on the NAS cluster master node:
> nas nfsv4 enable
NFSv4 successfully enabled only on this node.
Other nodes are unaffected.
> nascluster set nfs-ha on
To enable NFS-HA(v4), you must unmount all NFS clients from all nodes in the cluster.
All clients must re-mount with node virtual addresses.
Are you sure you want to enable NFS-HA(v4)? (yes/No)? yes
NAS Cluster setting NFS-HA: yes (v3=yes, v4=yes, legacy_ha=yes)
Verifying all nodes set to NFSv4=yes
NAS Cluster applying NFS-HA yes (v3=yes, v4=yes, legacy_ha=yes) settings ...
Updating system NAS cluster configuration ...
NFS: services (v4=yes, v3=no, HA=yes)
Check for master takeover ...
Publish master configuration ...
...
Cluster verification of 192.168.16.10 successful ...
NFS-HA(v4) successfully enabled.
NFS clients must mount using a VIP configured for the NAS cluster.
Scale-out NFS-HA v3 and NFS-HA v4
If you set a scale out configuration using a VIP pool, then the NFS-HA is activated when the cluster is created. If at the time of the cluster creation NFSv4 is also enabled, then you have an NFS-HA configuration for both NFSv3 and NFSv4.
A client can NFS mount any of the IP addresses in the VIP pool, except the master VIP.
If the cluster already exists with NFSv3 only, then you must disable NFS-HA on the master node and enable NFSv4 before you enable NFS-HA.
Do the following on the nascluster master node:
> nascluster set nfs-ha off
To disable NFS-HA(v3), you must unmount all NFS clients.
Are you sure you want to disable NFS-HA(v3)? (yes/No)? yes
NAS Cluster setting NFS-HA: no (v3=yes, v4=no, legacy_ha=no)
NAS Cluster applying NFS-HA no (v3=yes, v4=no, legacy_ha=no) settings ...
Updating system NAS cluster configuration ...
NFS: services (v4=no, v3=yes, HA=no)
Check for master takeover ...
Publish master configuration ...
Sending local auth-config sync to ...
Broadcasting share config-sync to NAS cluster ...
Broadcasting share config-sync to NAS cluster ...
Cluster verification for 192.168.16.10 in-progress ...
Verification of SNFS root, shared directories, nodes file for 192.168.16.10 in-progress ...
Verification of SNFS root, shared directories, nodes file for 192.168.16.10 successful ...
Node state: pnn:0 192.168.16.10 OK (THIS NODE)
Cluster verification of 192.168.16.10 successful ...
NFS-HA(v3) successfully disabled.
NFS services have been reset on all nodes.
> nas nfsv4 enable
NFSv4 successfully enabled only on this node.
Other nodes are unaffected.
> nascluster set nfs-ha on
To enable NFS-HA(v4 and v3), you must unmount all NFS clients from all nodes in the cluster.
All clients must re-mount with cluster name: 'vop-pool.mdh.quantum.com'.
Are you sure you want to enable NFS-HA(v4 and v3)? (yes/No)? yes
NAS Cluster setting NFS-HA: yes (v3=yes, v4=yes, legacy_ha=no)
Verifying all nodes set to NFSv4=yes
NAS Cluster applying NFS-HA yes (v3=yes, v4=yes, legacy_ha=no) settings ...
Updating system NAS cluster configuration ...
NFS: services (v4=yes, v3=yes, HA=yes)
Check for master takeover ...
Publish master configuration ...
Sending local auth-config sync to ...
Broadcasting share config-sync to NAS cluster ...
Broadcasting share config-sync to NAS cluster ...
Cluster verification for 192.168.16.10 in-progress ...
Verification of SNFS root, shared directories, nodes file for 192.168.16.10 in-progress ...
Verification of SNFS root, shared directories, nodes file for 192.168.16.10 successful ...
Node state: pnn:0 192.168.16.10 OK (THIS NODE)
Cluster verification of 192.168.16.10 successful ...
NFS-HA(v4 and v3) successfully enabled.
NFS clients must mount using a VIP configured for the NAS cluster.
