solaris super cluster server cannot mount /nfs mount on vnx even though...

[admingirl]

Hello,

I created an NFS mount point on the VNX, added the hosts for read/write, root privileges. A new Oracle Super Cluster has been installed and I added the Super Cluster hosts.

We opened network ports for NFS to/from the the hosts to the VNX control station and primary data mover. Yet they still cannot mount the slices. Other hosts(not on the Super Cluster) on a different network can mount the nfs slices.

They are also using data pump.

Any input you have is greatly appreciated.

Admin

[dynamox]

super cluster, sounds important

can they run "showmount -e  datamover_interface"  from one of these hosts ?  This command will display all nfs exports available on that datamover.

[admingirl]

Thank you Dynamox! I will ask him to do that now.

[admingirl]

I got the group to give me a login and I executed the command it just hangs. The version is Solaris 11.

[dynamox]

what firewall ports did you open ? Something is still blocking it.

[admingirl]

Thank you Dynamox, we opened

(UDP, TCP both ways) on the primary data mover and control station. Did not open for the failover datamover. Could that be causing it?

111

2049

4045

1110

[admingirl]

2049, 4045 are for data pump

[dynamox]

admingirl wrote:

Thank you Dynamox, we opened
(UDP, TCP both ways) on the primary data mover and control station. Did not open for the failover datamover. Could that be causing it?

111

2049

4045

1110

you don't need control station for NFS/CIFS connectivity, management only.  Standby datamover will assume primary datamover's IP address so nothing special there either.

Could your firewall guys temporarily create a rule to all all ports between that host and the interface on VNX. If firewall is wide open for that host that it could be host related,  is there a local firewall on the host itself ?

[admingirl]

So I can login, but I found that the VNX file NFS default port is 2049. The Oracle super cluster is using 4045. My legacy linux servers use 2049.

I don't think I can change the default port and if I do, other stuff will not be working I don't think.

Admingirl

[zhaos2]

If other hosts can mount the NFS from the same VNX, it is more likely that the issue is with Solaris itself or network side.  Here are steps for troubleshooting:

1. From Solaris, ping the IP of data mover (the same IP which you use to mount the NFS export from VNX).  If ping is not working, it is a network issue.

1. If ping works fine, use “/usr/sbin/rpcinfo –p <datamover’s IP>” on Solaris to check if the ports 2049/1234/111 on data mover can be connected.  A normal output should be as below:

    # /usr/sbin/rpcinfo -p server_2 |egrep "portmap|nfs|mount"

    100003 2   udp   2049  nfs

    100003 3   udp   2049  nfs

    100003 2   tcp   2049  nfs

    100003 3   tcp   2049  nfs

    100005 3   tcp   1234  mountd

    100005 2   tcp   1234  mountd

    100005 1   tcp   1234  mountd

    100005 3   udp   1234  mountd

    100005 2   udp   1234  mountd

    100005 1   udp   1234  mountd

    100000 2   udp    111  portmapper

100000 2   tcp    111  portmapper

If there is no output or it is timed out, the issue should be that the network router between Solaris and VNX filters traffic on these ports.

1. If step 1 and 2 pass, on Solaris use “/usr/sbin/showmount –e <datamover’s IP>” to check the list of NFS exports.  If you can see the NFS export you want to mount, you can go ahead to mount it and see if there is any error.  Then the issue would be related with the NFS permission.

As per the problem description, I suppose the issue would be found from step 1 or step 2.