Skip to main content
NetApp Knowledge Base

ONTAP Tools for VMware vSphere (OTV ) fails to provision NFS datastore at both ESXi host and cluster level

Views:
127
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • ONTAP Tools for VMware vSphere (OTV )
  • VMware vSphere

Issue

  • OTV fails to provision NFS datastore at neither VMware ESXi host nor cluster level:

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.

  • In OTV log (Kamino.log) shows "Controller 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 OTV .

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device