The issue seems to be that Windows NFS uses non-monitored locks, which cDOT does not support currently. I have not seen an official statement, but supposedly there are plans to add this support to future releases.
The problem is that cDOT does not support the use of non-monitored locks, which is a Windows DOS portion of the RFC standard. Locks are provided by NLM in NFSv3.
So, as a workaround, you'd have to disable NLM on Windows NFS to use it with cDOT. Native Windows NFS does not support this (using nolock as a mount option is not the same), so the only way to get NFSv3 to work with cDOT in Windows is via 3rd party apps like OpenText/Hummingbird.
However, it's not recommended to use NFSv3 without locking. A better approach is to use NFSv4, which has integrated locking/leasing and no NLM. But again, no native Windows NFS support for NFSv4, so 3rd party app is the answer.
Unsupported in this case simply means it has not been tested with NetApp storage on cDOT, thus results and mileage may vary. But I know it works - I've gotten it to work.
TR-4067 will be getting a major update in the coming months with more info about the Windows NFS issue and a TR that explains how to use OpenText with cDOT for Windows NFS is in the works as well.
Please feel free to message me or respond to this thread if you have additional questions.
PCNFS, WebNFS, and HCLNFS are not supported with clustered Data...
Currently we need to migrate 7 mode volume to CMODE..but while we tested with NFS cmode volume on the legacy Windows nT,windows 95 with Hummingbird Tools cannot mount.
At the same time can mount in windows XP.
we are in the position of cannot do any migration if this cannot work , becuse we need to takeover same IP from old NAS for the new SVM...Also find some dcument shows NetApp doesnt support for Hummingbird...