The IBM TotalStorage NAS Gateway 500 Integration Guide

Chapter 13. Linux systems integration 379

100021 4 udp 32772 nlockmgr

100021 1 tcp 32773 nlockmgr

100021 2 tcp 32773 nlockmgr

100021 3 tcp 32773 nlockmgr

100021 4 tcp 32773 nlockmgr

100024 1 tcp 32774 status

100024 1 udp 32785 status

100133 1 tcp 32774

100133 1 udp 32785

200001 1 tcp 32774

200001 1 udp 32785

200001 2 tcp 32774

200001 2 udp 32785

In this example, the NFS server process is not listed in the registered programs

on NAS Gateway 500. So we know the NFS server on NAS Gateway 500 is not

up and running. If you get this problem, please review the NAS Gateway 500

setup process, and make sure there is no error reported during the NFS share

configuration.

The reverse lookup problem on Red Hat Linux

Sometimes you may get the error message shown in Example 13-9 while

mounting a NAS Gateway 500 NFS share on Red Hat Linux.

Example 13-9 Red Hat NFS mounting error 3

[root@naslinux root]# mount -t nfs 9.1.38.198:/Vols/FJL3VOL01 /mnt/nfs

mount: 9.1.38.198:/Vols/FJL3VOL01 failed, reason given by server: unknown nfs

status return value: -1

This is usually caused by the reverse lookup problem, which means NAS

Gateway 500 can’t resolve the IP address of the Red Hat Linux client to host

name.

You must configure name resolution on NAS Gateway 500 to fix this problem.

See “The reverse lookup problem on AIX” on page 366 for the detailed steps.

13.2 SUSE LINUX: Access a NAS Gateway 500 share

Here we explain how to access a NAS Gateway 500 NFS share from SUSE

LINUX. We also provide some troubleshooting information for integrating NAS

Gateway 500 with SUSE LINUX.

380 The IBM TotalStorage NAS Gateway 500 Integration Guide

13.2.1 Mounting a NAS Gateway 500 NFS share on SUSE LINUX

Here we discuss the mount command used to mount a NAS Gateway 500 NFS

share on SUSE LINUX, and how to make the NFS share mounted automatically

at system startup.

The mount command to use on SUSE LINUX

In order to mount a NAS Gateway 500 NFS share on SUSE LINUX, the mount

command should be used as shown in Example 13-10.

Example 13-10 NFS mount command on SUSE

naslinux:~ # mount -t nfs 9.1.38.198:/Vols/FJL3VOL01 /mnt/nfs

The -t option of the mount command on SUSE LINUX indicates the filesystem

type to be mounted. It should always be nfs while mounting a NAS Gateway 500

NFS share. You can also combine other mounting options with the mount

command. See the SUSE LINUX documents for a detailed description of

mounting options.

After the mount command is returned, you can run the mount command without

parameters to verify the mount status (Example 13-11).

Example 13-11 SUSE: the mount command output

naslinux:~ # mount

/dev/hda2 on / type reiserfs (rw)

proc on /proc type proc (rw)

devpts on /dev/pts type devpts (rw,mode=0620,gid=5)

shmfs on /dev/shm type shm (rw)

usbdevfs on /proc/bus/usb type usbdevfs (rw)

9.1.38.198:/Vols/FJL3VOL01 on /mnt/nfs type nfs (rw,addr=9.1.38.198)

The NFS share, mount point, filesystem type, and mount options are displayed

with this command.

Mount the NAS share automatically at system startup

In order to mount the NFS share automatically at SUSE LINUX startup, we can

either configure the NFS client in yast2, or edit the /etc/fstab file on SUSE LINUX.

The configuration of the NFS client with yast2 is very straightforward, and yast2

accomplishes this task by modifying the /etc/fstab file. The /etc/fstab file on

SUSE LINUX contains descriptive information about filesystem. It is processed

by the system scripts of SUSE LINUX during system startup. Our /etc/fstab is

shown in Example 13-12. See the SUSE LINUX documentation for a detailed

description of the /etc/fstab file.