Planning the Sun Cluster HA for NFS Installation and Configuration

This section contains the information that you need to plan the installation and configuration of your Sun Cluster HA for NFS.

Service Management Facility Restrictions

Starting with Solaris 10, the following Service Management Facility (SMF) services are related to NFS.

• /network/nfs/cbd

• /network/nfs/mapid

• /network/nfs/server

• /network/nfs/rquota

• /network/nfs/client

• /network/nfs/status

• /network/nfs/nlockmgr

The Sun Cluster HA for NFS data service sets the property application/auto_enable to FALSE and the property startd/duration to transient for three of these services.

• /network/nfs/server

• /network/nfs/status

• /network/nfs/nlockmgr

These property settings have the following consequences for these services.

• When services that depend on these services are enabled, these services are not automatically enabled.

• In the event of any failure, SMF does not restart the daemons that are associated with these services.

• In the event of any failure, SMF does not restart these services.

Loopback File System Restrictions

Do not use the loopback file system (LOFS) if both conditions in the following list are met:

• Sun Cluster HA for NFS is configured on a highly available local file system.

• The automountd daemon is running.

If both of these conditions are met, LOFS must be disabled to avoid switchover problems or other failures. If only one of these conditions is met, it is safe to enable LOFS.

If you require both LOFS and the automountd daemon to be enabled, exclude from the automounter map all files that are part of the highly available local file system that is exported by Sun Cluster HA for NFS.