When using the PRIMECLUSTER Wizard for NAS, take notice of the following:
If you use NAS resources in combination with other Wizard products like PRIMECLUSTER Wizard for Oracle, select NAS in the menu of the turnkey wizard in "2.5.2 userApplication creation".
Information
If you use NAS resources in combination with other Wizard products, select NAS in the following screen.
Creation: Application type selection menu: 1) HELP 2) QUIT 3) RETURN 4) OPTIONS 5) CRM 6) DEMO 7) GENERIC 8) NAS 9) NETAPP 10) NETWORKER 11) ORACLE 12) SYMFOWARE Application Type:8
ExportFlag (included in 4.3A10 or later) described in "2.5.2 userApplication creation" determines whether or not Export processing for NAS volumes is executed during Online processing. Up to the previous version, Export processing was always executed during Online processing.
If you set UnLockFlag to "always" in scalable operation, Unlock processing is executed during split brain. Then, NFS re-locking is executed, and the lock is set again, so this does not disrupt ongoing operations. But the NFS relocking might slow down operations.
If you specify IP instead of a NAS host name in /etc/fstab.pcl, the NFS lock control might fail. You must specify a host name.
When you register a host name of a cluster node in the hosts file of the NetApp Filer(7-Mode), the host name should be the same as the one that is registered in that cluster node. If it is different, the lock control might fail.
When you use a clustered NetApp Filer(7-Mode), you need to specify an export volume or qtree name in the "/etc/exports" file, so takeover/giveback will be properly performed.
When you use a clustered NAS, NAS does not temporarily respond during takeover/giveback. To prevent failover, you need to set both the ServerTimeout and Timeout of the RemoteFileSystems resource to about 300 seconds. The value varies depending on an environment.
In the following cases, NAS resource does not goes into Warning state.
- When control facility for the NetApp Filer-Cluster is not used in standby operation.
- When failover of the NAS device has been caused by manual operation or failure other than failure of network.
- When failover of the NAS device has been caused by the "Negotiated Failover for Networking" function of DataONTAP7.2 or later.
If NAS device after failover is recovered (giveback), discontinue monitoring NAS resources so that failover doesn't occur again while recovering.
Mount points controlled by PRIMECLUSTER are displayed by mount(1) or df(1) commands after userApplication transitioned to Online state and NAS volumes were mounted. The mount points listed in /etc/fstab.pcl are replaced with symbolic links to the mount points controlled by PRIMECLUSTER.
Example
# mount nas1:/vol/vol2 on /opt/SMAW/SMAWRrms/dev/nfs/RMSNFS10015_mountpoint1 type nfs (rw,hard,bg,nointr,rsize=32768,wsize=32768,tcp,nfsvers=3,addr=10.20.30.40) nas2:/vol/vol2 on /opt/SMAW/SMAWRrms/dev/nfs/RMSNFS10016_mountpoint2 type nfs (rw,hard,bg,nointr,rsize=32768,wsize=32768,tcp,nfsvers=3,addr=10.20.30.41) # df -h nas1:/vol/vol2 900M 1.5M 899M 1% /opt/SMAW/SMAWRrms/dev/nfs/RMSNFS10015_mountpoint1 nas2:/vol/vol2 900M 1.5M 899M 1% /opt/SMAW/SMAWRrms/dev/nfs/RMSNFS10016_mountpoint2 # ls -l /mountpoint1 lrwxrwxrwx 1 root root 47 May 31 18:07 /mountpoint1 -> /usr/opt/reliant/dev/nfs/RMSNFS10015_mountpoint1 # ls -l /mountpoint2 lrwxrwxrwx 1 root root 47 May 31 18:07 /mountpoint2 -> /usr/opt/reliant/dev/nfs/RMSNFS10016_mountpoint2 #
