On Solaris 10, you must disable the Service Management Facility (SMF) for the NFS daemons.
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 commands before bringing the NFS agent online or the agents returns an UNKNOWN state.
To keep nfsd and mountd daemons under VCS control, on all cluster nodes:
# svccfg -s nfs/server setprop "application/auto_enable = false"
# svcadm refresh nfs/server
# svcadm disable svc:/network/nfs/server:default
# svcs -a | grep -i nfs disabled May_29 svc:/network/nfs/server:default
To keep nfsmapid daemon under VCS control, on all cluster nodes:
# svccfg -s nfs/mapid setprop "application/auto_enable = false"
# svcadm refresh nfs/mapid
# svcadm disable svc:/network/nfs/mapid:default
# svcs -a | grep -i mapid disabled May_29 svc:/network/nfs/mapid:default
To keep the statd daemon under VCS control, on all cluster nodes:
# svccfg -s nfs/status setprop "application/auto_enable = false"
# svcadm refresh nfs/status
# svcadm disable svc:/network/nfs/status:default
# svcs -a | grep -i nfs disabled May_29 svc:/network/nfs/status:default
To keep lockd daemon under VCS control, on all cluster nodes:
# svccfg -s nfs/nlockmgr setprop "application/auto_enable = false"
# svcadm refresh nfs/nlockmgr
# svcadm disable svc:/network/nfs/nlockmgr:default
# svcs -a | grep -i nlockmgr disabled May_29 svc:/network/nfs/nlockmgr:default