Filter
Top Products
13.2 Checking NFS Server Status
Some DMS client boot problems occur if the DMS server is not a Network
File System (NFS) server. To check whether or not a DMS server is an NFS
server, enter the following command on the DMS server:
# rcmgr get NFSSERVING
If the response is a 1, the system is an NFS server. If the response is a 0, the
system is not an NFS server. Run nfsconfig to configure the server to be
an NFS server. See nfsconfig(8X) for more information.
13.3 Checking Network Daemon Status
Some DMS client boot problems occur if the network daemons are not
running on the DMS server. This condition is indicated on the DMS client
with a message similar to the following:
panic: vfs_mountroot: cannot mount root
If you see this message on the DMS client, make sure that the following
daemons are running on the DMS server:
• portmap
• mountd
• nfsd
• nfsiod
Enter the following command on the DMS server to see if the network
daemons are running:
# ps ax | grep -E "portmap|mountd|nfsd|nfsiod"
You see process status for any of those daemons that are running, as well
as a line showing your grep command. If the daemons are not all running,
you must start the inoperative ones.
13.4 Checking Directory Exports
Some DMS client boot problems occur if the client’s directories are not
exported correctly. If the DMS client boots to single-user mode but will
not boot to multiuser mode, look at the entries in the DMS server’s
/etc/exports file and ensure that the /usr file system and dmsN root area
entries in /etc/exports are correct, similar to the following example for a
DMS client named client1 registered to the /var/adm/dms/dms0.alpha
DMS area:
/clients/client1 -r=0 client1
/var/adm/dms/dms0.alpha/root/usr -r=0 -ro
See exports(4) for information about the /etc/exports file.
13–2 Troubleshooting DMS