NFSv4 Enhancements and Best Practices Guide: Data ONTAP Implementation
NFSv3, client-server communication happens using a numeric user ID and group ID (UID/GID)
NFSv4 does not support UID or GID; it supports string-based communication for users and groups between the server and the client. Therefore entry of users and groups must be in the local /etc/passwd file, whether in Network Information Service (NIS) or LDAP. This is a mandatory requirement when moving into an NFSv4 environment. If you are logging in as root or any other user, then there should be an identical entry in /etc/passwd and /etc/group on the NetApp system as well as on the client. However, you should not do this if the NetApp system and the clients are connected to the same NIS server.
UDP mount to TCP mount conversion. Because UDP is no longer supported, any existing mounts over UDP must be changed to TCP while moving to NFSv4.
If the user originates from a subdomain, then all the domains and the subdomains should be listed in the /etc/resolv.conf
That did not work either. If the real path on the Filer is /vol/vol4/test, is this what I should be mounting on the Linux client? (ie., mount.nfs4 filername:/vol/vol4/test /mnt)? I am confused by the pseudo-filesystems.