ESXi 6.0 Update 1 Problems with NFS Mounts

On my host i have a management NIC and and another Vkernal port group for vMotion only both are in the same vSwitch. Even though my management network is select as such I have mount my NFS store mappings are using my vMotion port group  but why if it is not select as a management network???
LVL 20
compdigit44Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
iSCSI and NFS traffic flows through a VMKernel Portgroup only.

use vmkping, to send traffic out of the vmkernel portgroup you select, can it reach the NFS NAS.
0
compdigit44Author Commented:
I totaly understand the both iscsi and NFS use the VMKernel port group my problem is that it is not using the port group (management) port group that I had hoped and using the vmotion port group
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
can you screenshot your vSwitch, and list IP Addresses....especially your NFS NAS
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

compdigit44Author Commented:
I cannot upload a screen right now but I can discrible the layout.

Our management / NFS / vmotion networks use vSwitch0 on a Standard Switch.
There are two port groups one VMkernel for management and the other for vmotion. The IP's for both are on the same vLan. The physical Nic's are set in an active / stand-by setup.

The IP range of the vmkernels is 192.x.x.x when the NFS target is on 10.x.x.x
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So you need an VMKernel IP Address of 10.x.x.x, to connect to a NAS of 10.x.x.x

if you using

vmkping -I <interface> 10.x.x.x.x

can you ping the NAS ?
0
compdigit44Author Commented:
I forgot to mention from my managment 192 address i can ping 10.xxx with out issue
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
is that ping or vmkping ?
0
compdigit44Author Commented:
Both ping and vmkping work without issue
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you can ping the NAS, and traffic is flowing through the correct network, and is somehow being routed to 10.x.x.x.x from 192.x.x.x

what is the NAS, and do you see the connection requests?

using vmkping, you can specify the vmk ports to send the correct packet to reach the NAS.
0
compdigit44Author Commented:
I think the issue is the fact my connect to my NFSISO store is using another VMKernal port group then expected..
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
which port is the traffic leaving ? IP Address ?

if there is a route to the NAS, it should connect....

if you can ping, look at logs, check NAS

what is the NAS ?

is this a new implementation?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if a packet for 10.x.x.x leaves the host, how does it know to get to 10.x.x.x

when you have a Management Network and vMotion on 192.x.x.x. ?

why don't you have a VMKernel Porgroup on 10.x.x.x.x
0
compdigit44Author Commented:
I am sorry but the network was set like this long before I started here. I was assume the vmkernel with the box management selected is the only NFS mounts would use and not a vmkernel port not selected as management but vmotion. I do know we use vlans and a lot of vlans are trunked
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
check the logs....

does the NFS mount request get to the NAS....

but where is the 10.x.x.x. NAS placed on the vMotion network, Management Network?

traffic going from 192, and getting to 10, must be routed?

unless you've just bunged a NAS on 10.x, on the 192 network.

is anything else connected to  the NAS ?

e.g. another ESXi server ?

or find a laptop, configure it and connect to the NAS
0
compdigit44Author Commented:
I am sorry for the late response my NFS server is a Winodws 2012 R2 server.  All of our VM I set the same wasy I only found this becuase I stated to lock down the NFS export and list IP that should connect and not everyone. I found I had to list the vmotion port group in some case since this was the one traffic was flowing out of and post likely has been going on for a while now.  You mention checking the logs which logs sir so I can tell which nic traffic is going out of.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
/var/log and event log on Windows 2012

with Windows 2012 R2, you may have to add the IP Addresses of the VMKernel Portgroups, if you have limited access by IP Address.

so you may have to add 192 & 10 addresses.
0
compdigit44Author Commented:
SO if I am limiting IP on my NFS share I may need to added bot my mgmt and vmotion IP's.... If so why? I am not trying to be a pain but trying to understand this better
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
because that is the IP Address the traffic is coming from as seen by the NFS server.
0
compdigit44Author Commented:
No way to force traffic through one specific port group??

Thank you as always :o)
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
well normally, you would have an VMKernel Portgroup with an IP Address on the same physical network and LAN as the IP Address of your iSCSI SAN or NFS NAS.

e.g. we have VMKernel Portgroups of 10.10.1.x and 10.10.2.x which exist on a VLAN, specific to NFS traffic, which connect to NetApp Filer (NFS), which has an IP Address of 10.10.1.100 and 10.10.2.200.

NFS traffic destined for SAN 10.10.1.100 goes out via the 10.10.1.x VMKernel Portgroup, and the reason for two different subnets 1.x and 2.x, is to provide different paths!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Author Commented:
I totally understand.. it is probably my lack of knowledge that is getting me here. I just do not understand why ESXi is select one adapter / port group over another..
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you must have a route, possibly configure to send the traffic through it.
0
compdigit44Author Commented:
I am going to look into this further tomorrow and let you know what I find out :0)
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
screenshots of networking would help further.

I cannot visualise your setup without!

and again vmkping is your friend here, you can use it to send (force) ping packets traffic via a specific vmkernel portgroups....

to find out for definite which vmk traffic is definitely leaving to the target IP address e.g. NAS
0
compdigit44Author Commented:
I just checked and and i do not have any explicit route..Please see the attached screen shot the vmotion and management port groups are on the same vLAN and the NFS storage is on another segement / vlan
Screenshot1.png
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, I can see three VMKernel Portgroups, 0,1 and 2, but the screenshot is as good as a "chocolate teapot" VLAN tags....

it has no IP Addresses....
0
compdigit44Author Commented:
Sorry the IP's of the VMkernals are 172.x.x.x and the NFS is 192.x.x.x

I had to blank out information for security reasons.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
those are private IP Addresses, there is nothing secret out them ?

and your NAS is 10.x.x.x ?
0
compdigit44Author Commented:
The NAS this host is connecting to is 192.x.x.x
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
before earlier you stated

NFS target is on 10.x.x.x
0
compdigit44Author Commented:
correct I have two NFS mounts both host having the same issue. Regardless I know this is only an issue because my lack of knowledge an appreciate your patience and going to close this question for now..
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, no problems.
0
compdigit44Author Commented:
You are always a great help.... so thanks again...
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No problems, I'll have to invite VMware Admins to an Advanced Troubleshooting VMware vSphere Day!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.