NFS in between HP-UX & Red Hat Linux

[praveen..]

Hi dave,
I tried with these options but it is not working..


#vi /etc/rc.config.d/nfsconf
#:::::::::::::
::::::::::::::
::::::::::::::

#LOCKD_OPTIONS=""
#STATD_OPTIONS=""
#MOUNTD_OPTIONS=""
LOCKD_PORT=4045
STATD_PORT=4046
MOUNTD_PORT=4047
#
# rpc.mountd configuration. See mountd(1m)
#
# START_MOUNTD: 1 if rpc.mountd should be started by a system startup script.
# 0 if /etc/inetd.conf has an entry for mountd.
# Note: rpc.mountd should be started from a system startup script,
# however, it can be started from either nfs.server or inetd, and
# MUST only be configured in one place.
#
START_MOUNTD=1
#
# AutoFS configuration. See automount(1m)
#
# In order to invoke the AUTOFS set the AUTOFS variable to 1.
#
# The 'nfs.client start' script will also use these variables
# to determine whether to start AutoFS or not during the boot
# sequence.
# AUTOFS = 0 - do not start AutoFS
# 1 - start AutoFS.
# AUTOMOUNT_OPTIONS= - options to the AutoFS automount command
# AUTOMOUNTD_OPTIONS= - options to the AutoFS automountd daemon
#
AUTO_MASTER="/etc/auto_master"
"/etc/rc.config.d/nfsconf" 70 lines, 2460 characters
:wq!



# /sbin/init.d/nfs.server stop
killing nfsd
killing rpc.mountd

# /sbin/init.d/nfs.client stop
killing automountd

# /sbin/init.d/nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 884
starting up the BIO daemons
/usr/sbin/biod 16
Reading in /etc/exports
starting up the Status Monitor daemon
rpc.statd already started, using pid: 19500
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 19506
AutoFS daemon already started, using pid: 19512
Running the AutoFS command interface
/usr/sbin/automount
mounting remote NFS file systems ...
mounting CacheFS file systems ...

# /sbin/init.d/nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 884
Reading in /etc/exports
starting up the mount daemon
rpc.mountd already started, using pid: 13441
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 19500
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 19506

# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100007 2 tcp 49152 ypbind
100007 2 udp 49153 ypbind
100007 1 tcp 49152 ypbind
100007 1 udp 49153 ypbind
100068 2 udp 49163 cmsd
100068 3 udp 49163 cmsd
100068 4 udp 49163 cmsd
100068 5 udp 49163 cmsd
100083 1 tcp 49153 ttdbserver
100024 1 tcp 56004 status
100024 1 udp 60396 status
100021 1 tcp 56005 nlockmgr
100021 1 udp 60401 nlockmgr
100021 3 tcp 56006 nlockmgr
100021 3 udp 60402 nlockmgr
100021 4 tcp 56007 nlockmgr
100021 4 udp 60403 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 56008 nlockmgr
100005 1 udp 57642 mountd
100005 3 udp 57642 mountd
100005 1 tcp 61021 mountd
100005 3 tcp 61021 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
#

I think this is a firewall issue in between hp-ux and linux server.

which ports should I need to get opened and on which server?

Please suggest, Thanks

[Dave Olker]

> # /sbin/init.d/nfs.server stop
> killing nfsd
> killing rpc.mountd
>
> # /sbin/init.d/nfs.client stop
> killing automountd

I never saw rpc.lockd or rpc.statd get terminated when you stopped the client and server. If they are not being stopped by these scripts then manually terminate them.

# /sbin/init.d/nfs.server stop
# /sbin/init.d/nfs.client stop
# kill $(ps -e | grep rpc.lockd | awk '{print $1})
# kill $(ps -e | grep rpc.statd | awk '{print $1})
# kill $(ps -e | grep rpc.mountd | awk '{print $1})

Then restart them:

# /sbin/init.d/nfs.client start
# /sbin/init.d/nfs.server start

Regards,

Dave

[praveen..]

I tried again stop / start.

# /sbin/init.d/nfs.server stop
killing nfsd
killing rpc.mountd
]
# /sbin/init.d/nfs.client stop
killing biod
killing automountd

#

# /sbin/init.d/nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 884
starting up the BIO daemons
/usr/sbin/biod 16
Reading in /etc/exports
starting up the Status Monitor daemon
rpc.statd already started, using pid: 19500
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 19506
AutoFS daemon already started, using pid: 19512
Running the AutoFS command interface
/usr/sbin/automount
mounting remote NFS file systems ...
mounting CacheFS file systems ...

# /sbin/init.d/nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 884
Reading in /etc/exports
starting up the mount daemon
rpc.mountd already started, using pid: 13441
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 19500
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 19506

#


But the problem is still there.

I think this is a firewall issue in between hp-ux (X.X.8.X) and linux server (X.X.79.X) different subnets.

which ports should I need to get opened and on which server?

Please suggest, Thanks

[Dave Olker]

Did you not read my last post? For some reason your lockd/statd daemons are not dying so manually terminate them.

The proof is when you try to start the scripts and it says:

starting up the Status Monitor daemon
rpc.statd already started, using pid: 19500
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 19506

That means they were not stopped when you shut down the scripts, so manually terminate the RPC daemons and try again.

Dave

[praveen..]

# ps -ef | grep -i rpc
root 884 1 0 Dec 15 ? 12:05 /usr/sbin/rpcbind
root 1335 1 0 Dec 15 ? 0:27 /opt/dce/sbin/rpcd
root 19500 1 0 Jan 17 ? 0:00 /usr/sbin/rpc.statd
root 19506 1 0 Jan 17 ? 0:00 /usr/sbin/rpc.lockd
root 22080 21578 0 16:03:53 pts/0 0:00 grep -i rpc
root 13441 1 0 Feb 2 ? 0:00 /usr/sbin/rpc.mountd

# kill -9 19506
]
# kill -9 19500

# kill -9 13441

# ps -ef | grep -i rpc
root 884 1 0 Dec 15 ? 12:05 /usr/sbin/rpcbind
root 1335 1 0 Dec 15 ? 0:27 /opt/dce/sbin/rpcd
root 22082 21578 0 16:04:39 pts/0 0:00 grep -i rpc


# /sbin/init.d/nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 884
starting up the BIO daemons
/usr/sbin/biod 16
Reading in /etc/exports
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
AutoFS daemon already started, using pid: 19512
Running the AutoFS command interface
/usr/sbin/automount
mounting remote NFS file systems ...
mounting CacheFS file systems ...

# /sbin/init.d/nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 884
Reading in /etc/exports
starting up the mount daemon
/usr/sbin/rpc.mountd
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 22122
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 22128

# ps -ef | grep -i rpc
root 884 1 0 Dec 15 ? 12:05 /usr/sbin/rpcbind
root 1335 1 0 Dec 15 ? 0:27 /opt/dce/sbin/rpcd
root 22206 21578 0 16:05:28 pts/0 0:00 grep -i rpc
root 22128 1 0 16:05:08 ? 0:00 /usr/sbin/rpc.lockd
root 22122 1 0 16:05:08 ? 0:00 /usr/sbin/rpc.statd
root 22165 1 0 16:05:22 ? 0:00 /usr/sbin/rpc.mountd

#


Problem is still there...


These servers are in different subnets

hp-ux (X.X.8.X) and linux server (X.X.79.X) different subnets.

which ports should I need to get opened and on which server?

Thanks

[Dave Olker]

Yes, I realize the problem is still there.

The question is - did the patches allow you to fix the port numbers on the server? If so then the rpcinfo -p output will tell you which ports you need to open on the firewall to allow traffic to those ports.

Dave

[praveen..]

On HP-UX:

# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100007 2 tcp 49152 ypbind
100007 2 udp 49153 ypbind
100007 1 tcp 49152 ypbind
100007 1 udp 49153 ypbind
100068 2 udp 49163 cmsd
100068 3 udp 49163 cmsd
100068 4 udp 49163 cmsd
100068 5 udp 49163 cmsd
100083 1 tcp 49153 ttdbserver
100024 1 tcp 51285 status
100024 1 udp 56327 status
100021 1 tcp 51286 nlockmgr
100021 1 udp 56330 nlockmgr
100021 3 tcp 51287 nlockmgr
100021 3 udp 56331 nlockmgr
100021 4 tcp 51288 nlockmgr
100021 4 udp 56332 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 51289 nlockmgr
100005 1 udp 56335 mountd
100005 3 udp 56335 mountd
100005 1 tcp 51290 mountd
100005 3 tcp 51290 mountd
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 udp 2049 nfs
100003 3 tcp 2049 nfs
#


On Red Hat Linux:

# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
100021 1 udp 35971 nlockmgr
100021 3 udp 35971 nlockmgr
100021 4 udp 35971 nlockmgr
100021 1 tcp 39422 nlockmgr
100021 3 tcp 39422 nlockmgr
100021 4 tcp 39422 nlockmgr
100011 1 udp 853 rquotad
100011 2 udp 853 rquotad
100011 1 tcp 856 rquotad
100011 2 tcp 856 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 880 mountd
100005 1 tcp 883 mountd
100005 2 udp 880 mountd
100005 2 tcp 883 mountd
100005 3 udp 880 mountd
100005 3 tcp 883 mountd
#


which ports should I need to get opened and on which server?

Thanks

[Dave Olker]

The HP-UX output shows the lockd/mountd/statd ports are still not using the ones you assigned. Are you absolutely sure you have PHNE_34550 and PHNE_34551 installed on this system?

[praveen..]

I think these patches are not installed.

# swlist -l product | grep PHKL_32713
PHKL_32713 1.0 nfs client hang; cache FS umount
# swlist -l product | grep PHNE_34550
# swlist -l product | grep PHNE_34551
# swlist -l patch | grep -i PHNE_34550
# swlist -l product | grep -e PHNE_34550
#

I will install these patches and then I will try again and let you know

Thanks for your help

[praveen..]

Hi Dave,
But I can mount this HP file system to Linux server of same subnet

but i cannt mount this HP file system to Linux server of different subnet.

so what you suggest

is it firewall issue or patch issue?

Thanks

[Dave Olker]

> But I can mount this HP file system to
> Linux server of same subnet
>
> but i cannt mount this HP file system to
> Linux server of different subnet.

This could be anything. Firewall, router configuration problem, cabling, switch, etc.

You said that rpcinfo failed between these hosts. Until you determine the underlying cause of that you'll never get NFS to work.

I said it *could* be a firewall issue and if it is then installing the patches, fixing the RPC program port numbers and configuring the firewall to allow traffic to those ports should resolve it. If there is no firewall between these systems then the problem is most likely a configuration issue in your network.

I can't tell you if you have a firewall in your network. If you don't know then you should be asking the people who manage your networking and security at your company.

Regards,

Dave

[praveen..]

Thanks,
I need to get firewall ports opened,
i didnt install the NFS more patches on hp-ux

Thanks