Talk with fellow users about the multiple protocols supported by NetApp unified storage including SAN, NAS, CIFS/SMB, NFS, iSCSI, S3 Object, Fibre-Channel, NVMe, and FPolicy.
Talk with fellow users about the multiple protocols supported by NetApp unified storage including SAN, NAS, CIFS/SMB, NFS, iSCSI, S3 Object, Fibre-Channel, NVMe, and FPolicy.
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
Some of our vservers that provide CIFS have a DNS alias. For each of the aliasses I created a HOST spn record. Although everything works fine I was wondering if a CIFS spn record is also recommended for each alias? Some Netapp documentation mentions HOST records, others mention CIFS records.
... View more
Hello all, I've been struggling to setup multipathing on an iSCSI boot LUN so after many days banging my head against a brick wall, I'm hoping somebody can point me in the right direction. Our development setup is as follows: FAS8200 running ONTAP 9.13.1P13 Cisco UCS X210c M7 blade server Oracle Linux 8.10 running 5.15.0-209.161.7.1.el8uek.x86_64 kernel Installation was fine, once I added ip=ibft to the boot command. I have setup two interfaces on the host and two on the FAS8200 vserver to cater for iSCSI and have established four paths: [root@vmhost-dev-b-02 ~]# iscsiadm --mode session tcp: [1] 10.31.5.101:3260,1026 iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 (non-flash) tcp: [2] 10.31.6.102:3260,1031 iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 (non-flash) tcp: [3] 10.31.6.101:3260,1030 iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 (non-flash) tcp: [4] 10.31.5.102:3260,1027 iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 (non-flash) I can see those sessions are logged on from the filer: fas8200a::> iscsi session show -vserver vsbidev1 -initiator-name iqn.2022-10.uk.ac.lboro:site-dev-b-iscsi-a:2 Tpgroup Initiator Initiator Vserver Name TSIH Name ISID Alias --------- ------- ---- ------------------------ --------- --------------------- vsbidev1 vsbidev1-01-a 2 iqn.2022-10.uk.ac.lboro:site-dev-b-iscsi-a:2 00:02:3d:00:00:01 vmhost-dev-b-02.lboro.ac.uk vsbidev1 vsbidev1-01-b 5 iqn.2022-10.uk.ac.lboro:site-dev-b-iscsi-a:2 00:02:3d:00:00:03 vmhost-dev-b-02.lboro.ac.uk vsbidev1 vsbidev1-02-a 2 iqn.2022-10.uk.ac.lboro:site-dev-b-iscsi-a:2 00:02:3d:00:00:04 vmhost-dev-b-02.lboro.ac.uk vsbidev1 vsbidev1-02-b 1 iqn.2022-10.uk.ac.lboro:site-dev-b-iscsi-a:2 00:02:3d:00:00:02 vmhost-dev-b-02.lboro.ac.uk 4 entries were displayed. Using NetApp's Linux Host Utilities I can see the LUN and four paths: [root@vmhost-dev-b-02 ~]# sanlun lun show controller(7mode/E-Series)/ device host lun vserver(cDOT/FlashRay) lun-pathname filename adapter protocol size product ---------------------------------------------------------------------------------------------------------- vsbidev1 /vol/vmhost_dev_b_02/rocky-dev-b-02 /dev/sdd host6 iSCSI 100g cDOT vsbidev1 /vol/vmhost_dev_b_02/rocky-dev-b-02 /dev/sdc host5 iSCSI 100g cDOT vsbidev1 /vol/vmhost_dev_b_02/rocky-dev-b-02 /dev/sdb host4 iSCSI 100g cDOT vsbidev1 /vol/vmhost_dev_b_02/rocky-dev-b-02 /dev/sda host3 iSCSI 100g cDOT But multipath refuses to see these devices as multipath devices: [root@vmhost-dev-b-02 ~]# multipath -l -v 3 Feb 13 14:26:14 | set open fds limit to 4096/262144 Feb 13 14:26:14 | loading /lib64/multipath/libchecktur.so checker Feb 13 14:26:14 | checker tur: message table size = 3 Feb 13 14:26:14 | loading /lib64/multipath/libprioconst.so prioritizer Feb 13 14:26:14 | foreign library "nvme" loaded successfully Feb 13 14:26:14 | sda: size = 209715200 Feb 13 14:26:14 | sda: vendor = NETAPP Feb 13 14:26:14 | sda: product = LUN C-Mode Feb 13 14:26:14 | sda: rev = 9131 Feb 13 14:26:14 | sda: h:b:t:l = 3:0:0:0 Feb 13 14:26:14 | sda: tgt_node_name = iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 Feb 13 14:26:14 | sdb: size = 209715200 Feb 13 14:26:14 | sdb: vendor = NETAPP Feb 13 14:26:14 | sdb: product = LUN C-Mode Feb 13 14:26:14 | sdb: rev = 9131 Feb 13 14:26:14 | sdb: h:b:t:l = 4:0:0:0 Feb 13 14:26:14 | sdb: tgt_node_name = iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 Feb 13 14:26:14 | sdc: size = 209715200 Feb 13 14:26:14 | sdc: vendor = NETAPP Feb 13 14:26:14 | sdc: product = LUN C-Mode Feb 13 14:26:14 | sdc: rev = 9131 Feb 13 14:26:14 | sdc: h:b:t:l = 5:0:0:0 Feb 13 14:26:14 | sdc: tgt_node_name = iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 Feb 13 14:26:14 | sdd: size = 209715200 Feb 13 14:26:14 | sdd: vendor = NETAPP Feb 13 14:26:14 | sdd: product = LUN C-Mode Feb 13 14:26:14 | sdd: rev = 9131 Feb 13 14:26:14 | sdd: h:b:t:l = 6:0:0:0 Feb 13 14:26:14 | sdd: tgt_node_name = iqn.1992-08.com.netapp:sn.c052244ddc6a11eeb08a00a098d45a03:vs.7 Feb 13 14:26:14 | dm-0: device node name blacklisted Feb 13 14:26:14 | dm-1: device node name blacklisted Feb 13 14:26:14 | dm-2: device node name blacklisted ===== paths list ===== uuid hcil dev dev_t pri dm_st chk_st vend/prod/rev dev_st 3:0:0:0 sda 8:0 -1 undef undef NETAPP,LUN C-Mode unknown 4:0:0:0 sdb 8:16 -1 undef undef NETAPP,LUN C-Mode unknown 5:0:0:0 sdc 8:32 -1 undef undef NETAPP,LUN C-Mode unknown 6:0:0:0 sdd 8:48 -1 undef undef NETAPP,LUN C-Mode unknown Feb 13 14:26:14 | libdevmapper version 1.02.181-RHEL8 (2021-10-20) Feb 13 14:26:14 | DM multipath kernel driver v1.14.0 Feb 13 14:26:14 | unloading const prioritizer Feb 13 14:26:14 | unloading tur checker I suspect the issue has something to do with the fact that root is sitting on this disk which is preventing is being changed. I've read suggestions that I need to enable multipathing at boot time and change the paths to the various partitions but I'm not sure if that will work or not. Any help or guidance would be gratefully received. Regards, Mark
... View more
