OTV fails to provision NFS datastore at both ESXi host and cluster level
Applies to
- ONTAP Tools for VMware vSphere (OTV )
- VMware vSphere
Issue
- OTV fails to provision NFS datastore:
Cannot create or mount NFS datastore because either none of your ESX host's VMkernel interfaces share a subnet with the controller or it would create anindirect data path. Try adding the network of the VMkernel interface(s) you'd like to use to mount to the default.allow.nfs.mount.networks property in the kaminoprefs.xml preferences file.
- OTV
kamino.log
showsController address ip_address dose NOT match VMkernel networks.
INFO [DatastoreIpHash] - DatastoreIpHash: Controller address xxx.xxx.xx.xx does NOT match VMkernel networks.
INFO [DatastoreIpHash] - DatastoreIpHash: Controller address xxx.xxx.xx.xx does NOT match VMkernel networks.
INFO [DatastoreIpHash] - DatastoreIpHash: Controller address xxx.xxx.xx.xx does NOT match VMkernel networks.
- It works normally when create and mount NFS datastore manually in vCenter without using OTV