I can ping the filer from the esx host and vice versa, but I have 4 interfaces on my esx servers, which one needs to resolve
1 for vmotion 1 for service console <---- I believe this is the network that the NFS traffic will be using??? 1 for production network 1 for dmz network
which leads me to more questions 1) i will be needing to connect to separate test network, user acceptance network and possibly one more. in addition to the ones above. Any problems I need to worry about for having 6-7 network interfaces. 2) Right now, I have all VM's datastores on SAN via FC HBAs. If I max out a server (30-35 VM's per host), will I need more than 1 GigE for NFS traffic if I move all VM datastores to NFS?
Thanks
Nils Vogels wrote:
Check your DNS / name resolving settings. 90% of the time, that's where your problem lies :-)
On 7/19/07, Jack Lyons jack1729@gmail.com wrote:
I am new to using esx on nfs. I have create an nfs export but when I try to mount it from the esx box, it is really slow - it takes 2- 3 minutes to mount?
I assume that isn't normal, but I am not sure where to start looking for problems. I assume it is probably doing something and then waits until a timeout occurs before proceeding with the mount. I can nfs mount the same filer / export on another box no problem (i.e. quickly)