NFS agent notes
Prev	File share agents	Next

---

NFS agent notes

The NFS agent has the following notes:

• Caveat when nodes in the cluster are a mix of AIX operating system versions 5.x and 6.1
• Using NFSv4
• Service Management Facility for Solaris 10

Caveat when nodes in the cluster are a mix of AIX operating system versions 5.x and 6.1

Failing over an exported file system between the NFS server nodes with different AIX operating system versions can result in a Stale file handle error at the NFS client. This issue is independent of VCS.

Using NFSv4

For NFS v4 support, you must specify the NFSv4Root attribute. You must include vers=4 in the Option attribute of the Share resource.

Set up Enterprise Identity Mapping (EIM) in the NFS environment, if:

• Mapping of userids and username is not same on both client and server
• Client and server belong to different domains

If either of the above points are true, and EIM is not set up, the client has minimal rights (user=nobody, group=nobody).

If you want to use the NFSv4 security feature, set the NFSSecurity attribute of the NFS resource to 1. Manually configure Kerberos or any other security environment that is supported by NFSv4.

Caveats

You export filesystems with NFSv4Root="/exp/exports1", and you forcefully stop the engine so that exports are still valid and existing. If you change configurations on NFS to set NFSv4Root="/newexport", the NFS Agent is not able to come online with this new root, because the already exported filesystem is using an older NFS pseudo file system root. To avoid this problem bring all Share resources down properly before changing NFSv4Root.

If you create a pseudo file system, a client can access the filesystem. After the NFS server fails over to the other system in the cluster, the client can not see the filesystem. The client needs to remount it.

Service Management Facility for Solaris 10

You must disable the Service Management Facility (SMF) for NFS daemons for the NFS agent to work on Solaris 10. SMF is the new service framework for Solaris 10. SMF provides an infrastructure to automatically start and restart services.

UNIX start-up scripts and configuration files previously performed these functions. SMF maintains the Service Configuration Repository to store persistent configuration information as well as runtime data for all the services. All NFS daemons (nfsd, mountd, etc.) are now controlled by SMF. To keep these daemons under VCS control, modify the configuration repository to disable the SMF framework for NFS daemons.

You must invoke the following command before bringing the NFS agent online or the agents returns an unknown state.

To keep nfsd and mountd daemons under VCS control

1. Set the auto_enable property to false.

   # svccfg -s nfs/server setprop "application/auto_enable = false"

2. Refresh the SMF configuration repository.

   # svcadm refresh nfs/server

3. Disable SMF.

   # svcadm disable svc:/network/nfs/server:default

4. Run svcs -a | grep -i nfs command and review its output to make sure that SMF for nfsd and mountd is disabled.

   # svcs -a | grep -i nfs

   disabled May_29 svc:/network/nfs/server:default

To keep nfsmapid daemon under VCS control

1. Set the auto_enable property to false.

   # svccfg -s nfs/mapid setprop "application/auto_enable = false"

2. Refresh the SMF configuration repository.

   # svcadm refresh nfs/mapid

3. Disable SMF.

   # svcadm disable svc:/network/nfs/mapid:default

4. Run svcs -a | grep -i mapid command and review its output to make sure that SMF for nfsmapid is disabled.

   # svcs -a | grep -i mapid

   disabled May_29 svc:/network/nfs/mapid:default