Open System Services NFS Management and Operations Guide

1. Run the SCF STATUS FILESET command.
• If there are problems with the OSS Monitor process ($ZPMON), correct them based on
data reported by the SCF STATUS FILESET command.
• If the OSS Monitor is functioning correctly, try to run OSS processes locally and access
the local file system.
2. If the problem still exists, proceed to “DP2”.
DP2
• To detect a problem with DP2 on systems running D-series RVUs:
1. Issue a Peripheral Utility Program (PUP) LISTDEV command.
If the disk on which your files reside is not up, bring up the drive with a PUP UP command.
2. Issue a File Utility Program (FUP) COPY command on the file that you suspect has a
problem.
Examine any error codes reported by FUP and examine the contents of the file if the FUP
COPY succeeds.
• To detect a problem with DP2 on NonStop systems running RVUs other than D-series RVUs:
1. Issue an SCF storage subsystem STATUS DISK command.
If the disk on which your files reside is not up, bring up the drive with an SCF storage
subsystem START DISK command.
2. Issue a FUP COPY command on the file that you suspect has a problem.
Examine any error codes reported by FUP and examine the contents of the file if the FUP
COPY succeeds.
Troubleshooting for Client Users
Table 3 (page 76) contains tips for recovering from errors that the client user might encounter.
Table 3 Troubleshooting for Client Users
Probable Causes and Possible CorrectionsClient Indicates
No Response 1. No network access path exists between the NFS client and OSS NFS server systems.
Check that the network connections are functional and that the user can use a form of
the ping command between the client and server. See “Client” (page 74).
Follow the strategy beginning with “SLSA or TLAM Subsystem” (page 74).
2. The PORTMAP process or the OSS NFS subsystem is not running on the system.
Check that OSS NFS is started on your server using the rpcinfo program on your PC
or workstation or on the NonStop system from a TACL prompt; enter this command:
rpcinfo -p [ hostname ]
where hostname is the name of the NonStop system that should be running your OSS
NFS server. Follow the strategy beginning with “OSS NFS Manager Process” (page 75).
Access Denied 1. The client specified an invalid mount point. The client user must correct the specified
mount point.
2. No OSS NFS server process is running for the specified mount point. Start the appropriate
OSS NFS server. See Chapter 4 (page 36), and to “SERVER Object” (page 30).
3. The client host is not permitted to use the specified mount point, because it was not
exported for that host. Export the mount point. See “EXPORT Object” (page 31).
4. The user name or password specified by the client system is not valid. The client user
must correct the value entered. If the value is correct, see Chapter 5 (page 57), and
“EXPORT Object” (page 31).
5. You attempted to access an object on a NonStop server that is protected by optional
OSS ACL entries, and server is running an RVU earlier than J06.09 or H06.20.
76 Troubleshooting