We have a vmware 6.7 environment where we use NFS datastores on a local NetApp... we then snapmirror these off site. We would like to be able to map them for restores from the remote site.
Out local NFS network isn't routed, so we have created a new VMK with new IPs (in another range) and a default gateway. We have verified that we are able to ping from the remote netapp to the vmk IPs.
But as we try to map a datastore either via snapcenter or even manually via vCenter, it fails. We think this is because it tries to use the wrong vmk... In vCenter 8 you actually get the option to choose which vmk you want to use as you map the datastore manuelly... (not sure if SnapCenter supports this)... but anyway is there a way to "fix" this? Or do we have to enable routing on our local NFS network?
#In SCV, is there a way to control which VMK is used for mapping a NFS datastore during restore?
valid knot
drowsy vale
I think the only way to do this is make sure that your vmk is in the same L2 net as your target (i.e. non-routed)
valid knot
We have other customers where the network is routed and where it works... this is iSCSI though, but the protocol shouldn't matter, so it works with routed networks... We have also checked that the exports created by SCV is correct and allows the correct access, so it may just be vmware that is not that clever in 6.7...
drowsy vale
yeah, it works if the first vmk adapter that can reach the IP is the correct one