I'm trying to get my NFS moved to a secondary network (with only my VM host) to try to help with performance.
My primary network is 192.168.2.0/23 with a gateway of 192.168.3.1. My VM Host is 192.168.2.80. I have a vswitch created in my current set up with a VM Port Group, VMKernel port and Service Console port with a single Physical Adapter vmnic0. The VM Kernel port has an IP of 192.168.2.113, and the service console port is also 192.168.2.80.
I tried adding a new vswitch and added a VMKernel port with an IP of 192.168.150.1. It's physical adapter is vmnic1, which properly shows link up when I connect it to my new switch. I changed the IP of my NAS device (Iomega StorCenter ix2-200) to be 192.168.150.10. I don't have a gateway or DNS, as I'm expecting to do everything by IP and I'm not worried about this network having internet access.
When I try to mount the NAS, it goes off for a few minutes and I get the following error:
Oct 31 10:16:05 192 vmkernel: 0:00:12:12.594 cpu2:4126)WARNING: NFS: 946: MOUNT RPC failed with RPC status 13 (RPC was aborted due to timeout) trying to mount Server (192.168.150.10) Path (/nfs/nas-datastore-01)
There are no permissions on the device, so I don't think it's that. Also, if I connect a laptop to the switch that they share and give myself a fixed IP in the network, I can get to everything just fine.
If I use the console, ping times out when trying to hit the device as well. However, vmkping will work if I specify "-I vmk1". This, to me, looks like a routing issue.
Unfortunately, I've used too many different combinations of things trying to get this to work to show the various outputs from "route -n" and "esxcfg-route -l". It does seem like route never showed any .150 networks, and esxcfg-route seemed to keep up pretty well with any changes I made.
I've tried this with and without the VMKernel port on the primary network. With and without the host itself set as the gateway for the VMKernel (.150.1). It always seems to time out.
Is there something basic that I'm missing? Can I do what I'm trying to accomplish? Given that my laptop can get in and communicate just fine, why can't ESX?
Any help would be appreciated!!
Matt