Have a working NFSv4 Kerberos Setup with netapp and Redhat.  Have to lifs. for example 1.1.1.1 and 2.2.2.2 with name lif1 and lif2. SVM1   can mount through 1.1.1.1 and 2.2.2.2. SVM1 has both ips in dns. I get access denied when i try to mount through SVM1. How to do this? Have also an spn for nvs/SVM1 and a host entry SVM1 in this Redhat IDM Kerberos domain.     ... View more

Hi, i try to use NFSv4 without ldap, because in this Area no ldap Server is available. On a other location i use NFSv4 with Kerberos and its working.    Created local Netapp Users and assigned v4 domain on Redhat. Cannot see the share at all with showmount -e. If i try nfs3 i can mount the share and write data. What am i missing?  ... View more

Are there any issues with using a unified VLAN for NFS and NVME-TCP traffic in a medium sized OpenShift VM environment?  For best performance, are separate VLANs best practice for data traffic for the backend storage with these two protocols?  According to NetApp’s Best Practices for Modern SAN (October 2025) for NVME-TCP traffic: Administrators may implement separate subnets and VLANs for logical traffic isolation. While redundant subnets strengthen resilience, distinct VLANs bolster security by maintaining discrete workflows.   Nothing specific to performance issues or gains.  ... View more

Hello all, I'm reviewing our current NFS client mount configuration and would like guidance on recommended NetApp NFS mount options for RHEL 9 clients. This is what we have for our nfsv3 shares: aplnas123:/nas123_vol013 /xxxx nfs auto,rw,defaults,intr 0 0 And this is what we have for our nfsv4 shares: aplnas123:/nas123_vol013 /xxxx nfs4 rw,nodev,noexec,nosuid 0 0 Should the NFS version (for example, vers=3, vers=4.1, or vers=4.2) be explicitly specified on RHEL 9 clients? Does anyone know whether these options are appropriate for RHEL 9 clients? If not, what would you recommend changing?   My understanding is that the "right" options may vary depending on business, performance, and application requirements, but I would appreciate any Linux or NetApp guidance to validate or tune the current setup.   Thanks. ... View more

Some years ago while trying to make multiprotocol shares work well accross a mixed bag of name services, we landed on configuring the data SVM to point to AD as the LDAP source. This seemed to solve several issues provided the accounts in AD have their unix attributes set, but we have since ran into issues around the "permission denied" due to too many groups, users being in substantially more than 16 groups, etc. Note the mixed bag means we have an entirely seperate LDAP DB which sort-of syncs from AD periodically, but it's a one-way street. Basically the NFS client machines do not use AD for LDAP but their own, and as such, the SVM can't talk to it to figure out group membership if the GID is beyond that 16 group limit. Rather than risk breaking multiprotocol shares does anyone know if multiprotocol and SMB-only shares would be affected if the SVM is pointed to the open LDAP server (is SMB dependant on AD LDAP lookups?) or since it looks like we need to enable auth-sys-extended-groups, would the better solution just be build a new SVM so it does nothing but NFS to that LDAP DB and essentially decouple NTFS from NFS entirely? thanks ... View more