This post is more than 5 years old
5 Posts
0
23426
August 9th, 2017 10:00
Cannot mount the NFS share from the simulator (8.1)
Hi,
Currently I am running a one node OneFS 8.1 simulator inside a Windows machine (using VMWare workstation). The host machine has the following ipconfig settings:
C:\Users\Administrator>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : eng.foo.com corp.foo.com
IPv6 Address. . . . . . . . . . . : fda7:e6ee:2e09:0:40e4:bc7a:f31e:cfca
Temporary IPv6 Address. . . . . . : fda7:e6ee:2e09:0:74bd:33f:85a0:30ec
Link-local IPv6 Address . . . . . : fe80::40e4:bc7a:f31e:cfca%11
IPv4 Address. . . . . . . . . . . : 10.2.41.210
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 10.2.32.1
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : fdfe:9042:c53d:0:1d12:a8ba:dcfa:33ee
Temporary IPv6 Address. . . . . . : fdfe:9042:c53d:0:1459:c35f:aba2:8d27
Link-local IPv6 Address . . . . . : fe80::1d12:a8ba:dcfa:33ee%20
IPv4 Address. . . . . . . . . . . : 192.168.117.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a91f:bc7e:625a:5659%21
IPv4 Address. . . . . . . . . . . : 192.168.77.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.eng.foo.com corp.foo.com:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : eng.foo.com corp.foo.com
Tunnel adapter isatap.{02DA5412-3A2A-4D54-BBDF-078B738030FB}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:14c3:31fa:f5fd:d62d
Link-local IPv6 Address . . . . . : fe80::14c3:31fa:f5fd:d62d%14
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.{05BA8BEE-F6D6-4603-B8B9-0A4FFB605DC9}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Then the Isilon node is configured with the following external and internal network:
Because I need to access the simulator node from outside the Windows host, I added the following port-forwarding rules on the Windows host:
C:\Users\Administrator>netsh
netsh>interface portproxy
netsh interface portproxy>show all
Listen on ipv4: Connect to ipv4:
Address Port Address Port
--------------- ---------- --------------- ----------
10.2.41.210 8080 192.168.77.2 8080
10.2.41.210 445 192.168.77.2 445
10.2.41.210 111 192.168.77.2 111
10.2.41.210 2049 192.168.77.2 2049
10.2.41.210 300 192.168.77.2 300
10.2.41.210 22 192.168.77.2 22
Then, I can access the web-ui and ssh with no problem from another machine (10.2.52.33) by accessing 10.2.41.210:8080 and 10.2.41.210:22.
However, I cannot access the NFS share, with the following error:
jason@view-jason-ubu:~/mount$ sudo mount -t nfs -o vers=3,ro 10.2.41.210:/ifs/jason isilon-jason/
mount.nfs: access denied by server while mounting 10.2.41.210:/ifs/jason
I have the following NFS share settings for that directory:
So I was just wondering, what is wrong in my configuration that prevents me from mounting the NFS share from 10.2.52.33? Please feel free to let me know if any additional information needs to be provided.
Thank you so much in advance!
Peter_Sero
4 Operator
•
1.2K Posts
0
August 9th, 2017 13:00
By design, NFS v3 uses variable=unpredictable port numbers, determined at startup
and announced through the "portmapper" service on fixed port 111.
Some NFS servers allow to configure fixeds port numbers for all NFS services,
but AFAIK that's not possible with OneFS.
Which leaves us with three alternatives:
1. The rpcinfo tool shows the currently choosen port numbers.
It is used by various scripts that have been written by firewall administrators
facing similar problems. Such scripts could serve as a start for
building an automated dynamic portproxy set-up.
2. Switching to NFS v4, which has fixed port numbers.
3. Using a "bridged network" set-up for the external interface of the Isilon VM.
This needs one more assigned address (like 10.2.41.211) for your physical network
to attach the VM right to the outside world.
hth
-- Peter
JasonTsai
5 Posts
0
August 9th, 2017 15:00
Hi Peter,
Thank you very much for your answers! I tried NFS v4 and it works great!
Although I do want to make option 3 to work, so that I can also use v3. I have added another adapter (10.2.39.67) for my physical network:
I have also configured an interface on the VM to be bridged to that physical adapter:
In this case, how should I set the IP address on that bridged interface in the vm? I suppose I cannot use the same ip which is 10.2.39.67, right? If it will be a different IP, then how from the outside world can I connect to this new IP?
Thanks again
Peter_Sero
4 Operator
•
1.2K Posts
0
August 10th, 2017 15:00
The identical IP is used on the physical interface and for the VM,
"as if" the VM was physically connected to the outside network just like a physical server.
This is what makes it so simple...
BTW in the VM config you could also use the preconfigured bridged network (vmnet0)
via the first option "Bridged: Connected directly..."
But customizing vmnet9 will also do.
-- Peter
JasonTsai
5 Posts
0
August 11th, 2017 10:00
Thank you again for your help, it works great now.
Regards,
Zheng