Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
SOLVED
Hi Praveen,
Have you actually tried mounting the filesystem and had a problem or are you just asking if it's possible? If you're just asking - yes, it's possible and works just fine. If you're seeing a problem please tell us what the problem is so we can help isolate it.
By the way, NFSv4 has never been offered for 11.23, ever. It is available on 11i v3 (11.31) but not on 11i v2 (11.23). However, even if your server supports NFSv4, every server I've ever seen will always negotiate the highest available NFS version supported by both the client and server. So if you're using a RedHat server that supports NFSv4 and an HP-UX client that only supports NFSv3 you'll get a V3 mount without incident.
Please tell us if you're actually seeing a problem when mounting between HP-UX and RedHat.
Thanks,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Have you actually tried mounting the filesystem and had a problem or are you just asking if it's possible? If you're just asking - yes, it's possible and works just fine. If you're seeing a problem please tell us what the problem is so we can help isolate it.
By the way, NFSv4 has never been offered for 11.23, ever. It is available on 11i v3 (11.31) but not on 11i v2 (11.23). However, even if your server supports NFSv4, every server I've ever seen will always negotiate the highest available NFS version supported by both the client and server. So if you're using a RedHat server that supports NFSv4 and an HP-UX client that only supports NFSv3 you'll get a V3 mount without incident.
Please tell us if you're actually seeing a problem when mounting between HP-UX and RedHat.
Thanks,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
From the RedHat system, try issuing these commands:
# rpcinfo -t nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
# rpcinfo -t mount
program 100005 version 1 ready and waiting
rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
program 100005 version 2 is not available
program 100005 version 3 ready and waiting
# rpcinfo -t nlockmgr
program 100021 version 1 ready and waiting
rpcinfo: RPC: Procedure unavailable
program 100021 version 2 is not available
program 100021 version 3 ready and waiting
program 100021 version 4 ready and waiting
# rpcinfo -t status
program 100024 version 1 ready and waiting
This will at least confirm that the RedHat client can communicate with the various daemons on the HP-UX server.
If all of the above rpcinfo commands return the expected results then I would verify the target filesystem is exported as you expect. On the NFS server issue this command:
# cat /etc/xtab
Verify the filesystem is exported with the permissions you expect and verify the RedHat client is included in any access lists associated with the target filesystem.
I would then enable debug rpc.mountd logging on the HP-UX server:
# kill -17 $(ps -e | grep mountd | awk '{print $1}')
Finally, try the NFS mount again and see what kind of messages are logged in the /var/adm/mountd.log file on the NFS server. This should show the MOUNT request coming in from the RedHat system and whether it is accepted or denied.
This will hopefully steer us in the right direction. There may be other data to collect, based on what this data shows, but this is what I'd collect first.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
# rpcinfo -t
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
# rpcinfo -t
program 100005 version 1 ready and waiting
rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
program 100005 version 2 is not available
program 100005 version 3 ready and waiting
# rpcinfo -t
program 100021 version 1 ready and waiting
rpcinfo: RPC: Procedure unavailable
program 100021 version 2 is not available
program 100021 version 3 ready and waiting
program 100021 version 4 ready and waiting
# rpcinfo -t
program 100024 version 1 ready and waiting
This will at least confirm that the RedHat client can communicate with the various daemons on the HP-UX server.
If all of the above rpcinfo commands return the expected results then I would verify the target filesystem is exported as you expect. On the NFS server issue this command:
# cat /etc/xtab
Verify the filesystem is exported with the permissions you expect and verify the RedHat client is included in any access lists associated with the target filesystem.
I would then enable debug rpc.mountd logging on the HP-UX server:
# kill -17 $(ps -e | grep mountd | awk '{print $1}')
Finally, try the NFS mount again and see what kind of messages are logged in the /var/adm/mountd.log file on the NFS server. This should show the MOUNT request coming in from the RedHat system and whether it is accepted or denied.
This will hopefully steer us in the right direction. There may be other data to collect, based on what this data shows, but this is what I'd collect first.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Sounds like a networking problem. Are you able to communicate with any other networking protocols between these two systems?
linkloop
ping
ftp
rcp
telnet
ttcp
netperf
Do all of those programs work as expected between these two systems? If these programs work and only NFS doesn't then I'd suggest taking a network trace of the failing rpcinfo commands to see if the trace shows the RPC packet leaving the RedHat box and never getting a reply from the HP-UX box.
Is there any firewall between these systems? IP Filter? Anything else that would restrict packets destined for specific port numbers?
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
linkloop
ping
ftp
rcp
telnet
ttcp
netperf
Do all of those programs work as expected between these two systems? If these programs work and only NFS doesn't then I'd suggest taking a network trace of the failing rpcinfo commands to see if the trace shows the RPC packet leaving the RedHat box and never getting a reply from the HP-UX box.
Is there any firewall between these systems? IP Filter? Anything else that would restrict packets destined for specific port numbers?
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Hi Vipin,
What OS is the HP-UX system running?
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
What OS is the HP-UX system running?
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
11.23 - that's good news.
If you have installed patch PHNE_34550 and PHNE_34551 (or any patches that supersede them) you can add the following lines to the /etc/rc.config.d/nfsconf file on the NFS server:
LOCKD_PORT=
STATD_PORT=
MOUNTD_PORT=
This allows you to configure static port numbers for rpc.lockd, rpc.statd and rpc.mountd. This means they will always start using the same port numbers, which makes configuring a firewall infinitely easier than before these fixes.
I recommend setting LOCKD_PORT to 4045 since that is the industry standard port number for rpc.lockd. I would then set STATD_PORT to 4046 and rpc.mountd to 4047. Like this:
LOCKD_PORT=4045
STATD_PORT=4046
MOUNTD_PORT=4047
Then you stop/start the nfs.client and nfs.server scripts:
# /sbin/init.d/nfs.server stop
# /sbin/init.d/nfs.client stop
# /sbin/init.d/nfs.client start
# /sbin/init.d/nfs.server start
and the newly running rpc.lockd, rpc.mountd and rpc.statd should be using the static port numbers. You can confirm this with an rpcinfo -p command, like this:
# 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
100024 1 udp 4046 status
100024 1 tcp 4046 status
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 1 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100005 1 udp 4047 mountd
100005 3 udp 4047 mountd
100005 1 tcp 4047 mountd
100005 3 tcp 4047 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
As you can see, the daemons are now registering at the configured ports. You also need to include ports 111 (rpcbind) and 2049 (nfsd). These patches make configuring a firewall or IP Filter much easier than without them.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
If you have installed patch PHNE_34550 and PHNE_34551 (or any patches that supersede them) you can add the following lines to the /etc/rc.config.d/nfsconf file on the NFS server:
LOCKD_PORT=
STATD_PORT=
MOUNTD_PORT=
This allows you to configure static port numbers for rpc.lockd, rpc.statd and rpc.mountd. This means they will always start using the same port numbers, which makes configuring a firewall infinitely easier than before these fixes.
I recommend setting LOCKD_PORT to 4045 since that is the industry standard port number for rpc.lockd. I would then set STATD_PORT to 4046 and rpc.mountd to 4047. Like this:
LOCKD_PORT=4045
STATD_PORT=4046
MOUNTD_PORT=4047
Then you stop/start the nfs.client and nfs.server scripts:
# /sbin/init.d/nfs.server stop
# /sbin/init.d/nfs.client stop
# /sbin/init.d/nfs.client start
# /sbin/init.d/nfs.server start
and the newly running rpc.lockd, rpc.mountd and rpc.statd should be using the static port numbers. You can confirm this with an rpcinfo -p command, like this:
# 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
100024 1 udp 4046 status
100024 1 tcp 4046 status
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 1 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100005 1 udp 4047 mountd
100005 3 udp 4047 mountd
100005 1 tcp 4047 mountd
100005 3 tcp 4047 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
As you can see, the daemons are now registering at the configured ports. You also need to include ports 111 (rpcbind) and 2049 (nfsd). These patches make configuring a firewall or IP Filter much easier than without them.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
