[nfs-discuss] NVFv3 mount issues on Solaris 10 Client from a Linux Server

2008-09-24 Thread Kumar, Amit H.
Hi Leal:

I was able to solve the problem ...it was a firewall issue. I enabled 
appropriate settings in iptables which took care of the issue.

Really thank you for your response!!!
Amit

> -Original Message-
> From: nfs-discuss-bounces at opensolaris.org [mailto:nfs-discuss-
> bounces at opensolaris.org] On Behalf Of Marcelo Leal
> Sent: Wednesday, September 24, 2008 11:10 AM
> To: nfs-discuss at opensolaris.org
> Subject: Re: [nfs-discuss] NVFv3 mount issues on Solaris 10 Client from
> a Linux Server
>
> What rpcinfo -p localhost says to you?
>
>  Leal
> --
> This message posted from opensolaris.org
> ___
> nfs-discuss mailing list
> nfs-discuss at opensolaris.org



[nfs-discuss] NVFv3 mount issues on Solaris 10 Client from a Linux Server

2008-09-24 Thread Marcelo Leal
What rpcinfo -p localhost says to you?

 Leal
--
This message posted from opensolaris.org



[nfs-discuss] NVFv3 mount issues on Solaris 10 Client from a Linux Server

2008-09-11 Thread Kumar, Amit H.
Hello Everyone,

This topic seems to be a old one but for some reason I am not able to get this 
to work.
Sorry for a long post ... wanted to get everything in at once!

Scenario:
Linux NFS server: v3
Solaris 10 NFS Client: v3

Problem mounting a NFS mount point from a Linux Server (CentOS 5.1 Kernel: 
2.6.18) to a Solaris 10 Client

My /etc/hosts.allow on Linux Server:
cat /etc/hosts.allow
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
portmap: 172.25.30.100
rpcbind: 172.25.30.100



Commands run on Client:
==
Client # mount -o vers=3 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: retrying: /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive

# mount -o vers=4 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120:/scratch/pvfs2: No such file or directory  <=== This 
error is because Linux Server is not running v4 NFS hence a valid one.

Client # rpcinfo -p
program vers proto port service
10 4 tcp 111 rpcbind
10 3 tcp 111 rpcbind
10 2 tcp 111 rpcbind
10 4 udp 111 rpcbind
10 3 udp 111 rpcbind
10 2 udp 111 rpcbind
1073741824 1 tcp 36084
100024 1 udp 42835 status
100024 1 tcp 36086 status
100133 1 udp 42835
100133 1 tcp 36086
11 2 udp 42836 rstatd
11 3 udp 42836 rstatd
11 4 udp 42836 rstatd
12 2 tcp 36087 rusersd
12 3 tcp 36087 rusersd
12 2 udp 42838 rusersd
12 3 udp 42838 rusersd
100011 1 udp 42840 rquotad
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr

# showmount -e 172.25.30.120 (Server)
showmount: 172.25.30.120: RPC: Rpcbind failure - RPC: Unable to receive

Commands OnServer:

Server # rpcinfo -p
program vers proto port
10 2 tcp 111 portmapper
10 2 udp 111 portmapper
100021 1 tcp 49927 nlockmgr
100021 3 tcp 49927 nlockmgr
100021 4 tcp 49927 nlockmgr
100021 1 udp 32772 nlockmgr
100021 3 udp 32772 nlockmgr
100021 4 udp 32772 nlockmgr
100011 1 udp 796 rquotad
100011 2 udp 796 rquotad
100011 1 tcp 799 rquotad
100011 2 tcp 799 rquotad
13 2 udp 2049 nfs
13 3 udp 2049 nfs
13 4 udp 2049 nfs
13 2 tcp 2049 nfs
13 3 tcp 2049 nfs
13 4 tcp 2049 nfs
15 1 udp 809 mountd
15 1 tcp 812 mountd
15 2 udp 809 mountd
15 2 tcp 812 mountd
15 3 udp 809 mountd
15 3 tcp 812 mountd
100024 1 udp 854 status
100024 1 tcp 857 status

Server # showmount -e 172.25.30.120
Export list for 172.25.30.120:
/scratch/nfs 172.25.30.100,172.25.24.0/4
/scratch/pvfs2 172.25.30.100,172.25.24.0/4

also tried to run Snoop on the client and wireshark on Server and following is 
what I see:

One Server: Upon issuing mount command on client:

# tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.00 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 
32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.205570 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(15) 
V:3 UDP
0.205586 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port 
unreachable)
0.207863 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(15) 
V:3 UDP
0.207869 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port 
unreachable)
2.005314 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 
32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
4.011005 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 
32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
5.206109 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 
172.25.30.120
5.206277 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 
00:14:4f:70:ff:17
5.216157 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(15) 
V:3 UDP
5.216170 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port 
unreachable)
...
On Clinet Upon issuing mount command on client:

# snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type= (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type= (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type= (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=15 (MOUNT) vers=3 
proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 
unreachable)
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=15 (MOUNT) vers=3 
proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 
unreachable)
? -> (multicast) ETHER Type= (LLC/802.3),