topic Not able to mount sharing folder in Operating System - HP-UX

Not able to mount sharing folder

yudhichandra — Mon, 18 Sep 2017 09:18:40 GMT

Hi all,

I have 3 servers, rx2600, rx2600, and rx2660.

I have another x86 server running on Suse, and create a shared folder named /public

From 1 of the rx2600 server I can mount that shared folder :

intaqa:/>mount 10.1.2.82:/public /bkup
intaqa:/>cd /bkup

But from 2 others server I am unable to mount that shared folder :

intabck:/>mount 10.1.2.82:/public /bkup
NFS server 10.1.2.82 not responding still trying

What should I check and change setting to solve this problem.

Thanks

Re: Not able to mount sharing folder

Matti_Kurkela — Tue, 19 Sep 2017 13:28:42 GMT

The error message indicates that the intabck server (the NFS client) is failing to communicate with the NFS server 10.1..2.82 over the network.

The cause could be:

- 10.1.2.82 server might not be configured to allow mounting the NFS share from the intabck server. (Is the /etc/exports or /etc/dfs/dfstab file configured correctly, and is the exportfs -ra or shareall command used to make all configuration updates effective?)

- if the mounting permission is defined by hostname, then the 10.1.2.82 server might be unable to resolve intabck's IP address back into a hostname, or the resolve operation is not returning the hostname you expect. (Test the IP-address -> hostname resolution using a method that actually uses the same data source(s) the system processes will use: on HP-UX you can use the nslookup command, but on Linux you should use "getent hosts <IP address>".)

- software firewall (ipf on HP-UX, iptables on Linux) blocking the connection on the NFS client or server (on HP-UX, if /etc/opt/ipf exists and is not empty, you may have IPFilter configured; on Linux, you can use "iptables -L -vn" to see any iptables filter ruleset if one exists.)

- hardware firewall in the network between the client and server

- network connectivity issue between the client and server (network misconfiguration, routing error, bad cable?)

Re: Not able to mount sharing folder

yudhichandra — Wed, 20 Sep 2017 01:23:16 GMT

Hi MK,

In my Linux server the /etc/exports contains this line only :

/public 10.1.2.0/20(rw,sync,no_root_squash,no_all_squash)

No I don't use hostname for mounting.

I can see the shared folder using showmount command..

There are some files in the /etc/opt/ipf folder

But files ipf.conf and ipnat.conf are empty.

What should I do next?

Thank you

Re: Not able to mount sharing folder

Matti_Kurkela — Thu, 21 Sep 2017 14:53:29 GMT

So, although the ipf configuration files are empty now, the system very likely has ipf installed. And it might have had ipf configured at some previous time.

Just emptying the configuration files won't erase the active ipf configuration from memory, unless the system is rebooted after that. To see if there are still any remaining ipf rules in effect, please run this command:

ipfstat -io

If it responds with:

empty list for ipfilter(out)
empty list for ipfilter(in)

then you can be sure there are no ipf rules in effect on the system.

If any ipf rules are still in effect, they can be deleted with:

ipf -Fa

---------------

You did not disclose the IP addresses of the rx26** servers having the problem: are they within the range of (10.1.0.0 .. 10.1.15.254) ? If not, then they are outside the range allowed by /etc/exports on the NFS server.

Can all the rx26** servers ping the 10.1.2.82 server successfully?

On the server having the problem, try running "rpcinfo -p". This lists the RPC services on that host.The list should include at least the portmapper/rpcinfo service and the status service. The list should appear pretty much immediately.

Then try running "rpcinfo -p 10.1.2.82": it will try and contact the RPC portmapper on the NFS server host and list the RPC services on the NFS server. You should get The list should include at least the rpcinfo/portmapper, status, mountd and nfs services, probably also the "nlockmgr" service. The listing should appear just about as quickly as the local RPC service listing. If there are delays, it suggests a problem connecting to TCP/UDP port 111 on the NFS server host, which will also cause problems with NFS.

You can also try and diagnose the problem using the "telnet" command.

On the rp26** hosts with the problem, try running this command:

telnet 10.1.2.82 111

If it responds with "Connected to 10.1.2.82", "Connection established" or equivalent, the network connection to TCP port 111 on the NFS server host is successful. If it hangs up to a minute and then responds with a "Connection timed out" message, it typically means a routing problem, or a firewall configured to drop the connection. If it responds immediately with a "Connection refused" message, it might mean the service is not actually running on the server host.

On a Linux system, /etc/hosts.allow and /etc/hosts.deny can also be used to restrict access to (some of) the NFS component services. If /etc/hosts.deny includes ALL:ALL (= the standard default "deny everything unless explicitly allowed" rule), you'll probably want to add something like this to /etc/hosts.allow on the NFS server host to ensure that the NFS component services on the NFS server are accessible to the hosts you wish to export NFS filesystems to:

rpcbind: 127.0.0.1 10.1.0.0/20
mountd: 127.0.0.1 10.1.0.0/20
statd: 127.0.0.1 10.1.0.0/20

Note that unless otherwise configured, the port numbers of some NFS component services (mountd, statd, nfslock) may change each time the respective server is restarted. This makes it extremely tricky to get NFS connections through firewalls. Fortunately, with both HP-UX and Linux, it is possible to set static port numbers for each service.

Re: Not able to mount sharing folder

yudhichandra — Fri, 22 Sep 2017 01:13:59 GMT

Hi MK,

This the resut for

intabck:/>ipfstat -io
empty list for ipfilter(out)
empty list for ipfilter(in)
intabck:/>

The ip address of others server :

rx2600 : 10.1.2.6 (intaqa) ----> this one can mount

rx2660 : 10.1.2.8 (intabck)

rx2800 : 10.1.2.4 (intadb)

rx2800 : 10.1.2.103 (intaaapp2)

and all can ping to 10.1.2.82

the result from telnet 10.1.2.82 111 are:

intaqa:/>telnet 10.1.2.82 111
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
Connection closed by foreign host.

intabck:/>telnet 10.1.2.82 111
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
Connection closed by foreign host.

intaapp2:/>telnet 10.1.2.82 111
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
Connection closed by foreign host.

In the /etc/hosts.allow there are no entry, all are marked by #

and I add entries :

rpcbind: 127.0.0.1 10.1.0.0/20
mountd: 127.0.0.1 10.1.0.0/20
statd: 127.0.0.1 10.1.0.0/20

In the /et/hosts.deny has 1 entry :

http-rman : ALL EXCEPT LOCAL

What should I do next?

Thank you

Re: Not able to mount sharing folder

Matti_Kurkela — Fri, 22 Sep 2017 09:58:12 GMT

OK, so the rpcbind/portmapper connection works on all the rx servers, and ipf is definitely not active. Good.

By the way, which HP-UX version is used on the rx servers? HP-UX 11.31 or older?

The next point to check would be the connectivity from the rx servers to the main NFS service port (2049).

Please run this command on all the rx servers:

telnet 10.1.2.82 2049

This needs also connect successfully for NFS service to work.

What is the output of "rpcinfo -p 10.1.2.82"?

The next step would be to identify the TCP port number of the "mountd" service in the "rpcinfo -.p 10.1.2.82" listing, and use the telnet command to verify connectivity from the rx servers to the NFS server for that port too.

If that is successful, you can also try running "showmount -e 10.1.2.82" on the rx servers. This command will communicate with the NFS mountd service on the NFS server, and produce a list of available NFS shares on the NFS server. If this command hangs or produces errors, then the communication with the mountd service is failing... and without it, NFS filesystem cannot be mounted.

Note that unlike the rpcbind/portmapper port (always 111) and the main NFS service port (always 2049), the port numbers of the remaining NFS component services can vary each time the services are restarted.

Re: Not able to mount sharing folder

yudhichandra — Mon, 25 Sep 2017 01:18:51 GMT

Hi MK,

Thanks for your responds.

The result :

intabck:/>telnet 10.1.2.82 2049
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.

intabck:/>rpcinfo -p 10.1.2.82
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecifi
ed error)
intabck:/>showmount -e 10.1.2.82
export list for 10.1.2.82:
/public 10.1.2.8/24
intabck:/>

intaqa:/>telnet 10.1.2.82 2049
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.

intaqa:/>rpcinfo -p 10.1.2.82
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
100005 1 udp 58286 mountd
100005 1 tcp 49516 mountd
100005 2 udp 58566 mountd
100005 2 tcp 51156 mountd
100005 3 udp 39827 mountd
100005 3 tcp 56390 mountd
100024 1 udp 53581 status
100024 1 tcp 42035 status
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 2 tcp 2049
100227 3 tcp 2049
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100227 2 udp 2049
100227 3 udp 2049
100021 1 udp 41197 nlockmgr
100021 3 udp 41197 nlockmgr
100021 4 udp 41197 nlockmgr
100021 1 tcp 52940 nlockmgr
100021 3 tcp 52940 nlockmgr
100021 4 tcp 52940 nlockmgr
intaqa:/>showmount -e 10.1.2.82
export list for 10.1.2.82:
/public 10.1.2.8/24
intaqa:/>

intaapp2:/>telnet 10.1.2.82 2049
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.

intaapp2:/>rpcinfo -p 10.1.2.82
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecifi
ed error)
intaapp2:/>showmount -e 10.1.2.82
export list for 10.1.2.82:
/public 10.1.2.8/24
intaapp2:/>

Re: Not able to mount sharing folder

yudhichandra — Mon, 25 Sep 2017 03:02:00 GMT

When I tried to telnet the mountd ports and the results are :

intabck:/>telnet 10.1.2.82 49516
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
♥
♥
Connection closed by foreign host.
intabck:/>telnet 10.1.2.82 56390
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
♥♥
Connection closed by foreign host.
intabck:/>telnet 10.1.2.82 51156
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
♥
♥

intaqa:/>telnet 10.1.2.82 49516
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
♥
♥
Connection closed by foreign host.
You have mail in /var/mail/root
intaqa:/>telnet 10.1.2.82 51156
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.
♥
♥

intaqa:/>telnet 10.1.2.82 56390
Trying...
Connected to 10.1.2.82.
Escape character is '^]'.

Re: Not able to mount sharing folder

yudhichandra — Thu, 05 Oct 2017 02:20:37 GMT

Hi all,

I have a good news, all my servers can mount to NFS server.
I seems one of my switch blocking NFS handshake.
Thank you a lot everyone for helping me.

Regards