Following is the situation:
We are using an ESXi host for demo purposes with direct-attached storage. To be able to create extra data-stores we have directly attached a NetApp system to serve as NFS server. The reason we attached the NetApp directly to ESXi host is the lack of available switch ports.
There is a default TCP/IP stack with 172.16.x.x network. I have added a new TCP/IP stack for NFS traffic (192.168.100.0/24). I created a new standard vSwitch with VMkernel port (vmk1) for NFS traffic. The VMkernel port has IP-address 192.168.100.101. I have also added the vmnic which is attached to NetApp port to the new vSwitch. For some reason I cannot get traffic to 192.168.100.0/24 to go through VMkernel port vmk1. I cannot add a static route because I have no default gateway for this subnet.
NetApp data-lif serving NFS has IP-address 192.168.100.100. From the NetApp data-lif I can reach (ping) the address of the VMkernel port vmk1 (192.168.100.101).
But a traceroute from ESXi shell to NetApp data-lif 192.168.100.100 tries to connect through VMkernel port vmk0 (172.16.x.x).
Can someone please share some light on this....or perhaps point me in the right direction?!
Thanks in advance!