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.
I have a query regarding the compatibility between nfsd and glibc. In our system, we've upgraded glibc to version 2.40 and are using NFS version 2.1.1 with NFSv3. Previously, with glibc 2.23, everything was working fine, and we weren’t using libtirpc. However, after the glibc upgrade, libtirpc was included and enabled in NFS as well. Now, none of the NFS-related services (nfsd, rpc.statd, rpc.mountd, portmap) are running. When attempting to start nfsd, the following errors occur: "unable to set any sockets for nfsd" "writing fd to kernel failed: errno 89 (Destination address required)" or "errno 111 (Connection refused)" Console logs show: "svc: failed to register nfsdv3 RPC service (errno 111)." After upgrading glibc, the --enable-obsolete-rpc option has been removed from glibc. Can anyone provide guidance on how to debug or resolve this issue?
... View more
I inherited administration of an offline domain environment with a NetApp (OnTap 9.11) and no dedicated NTP appliance Because the environment is offline, we have significant issues with time skew from the hardware. While we are looking for a better solution, at this stage we manage it by manually fixing the time roughly every month. It appears that this also led the to the previous administrators giving up on using CIFS shares. The shares exist and there is evidence they tried to make it work. But ultimately the shares are empty and other arrangements through Windows VM's are currently employed...all of which are on old OS's and need to be updated. I've been given the task of trying to fix things...and I really don't want to build new Windows servers and kick the can further down the road. The immediate issue is the time skew/sync. I want to use the domain controller as the NTP server, at least this way, the time skew *should* be the same on all devices The NetApp was already configured to use the DC as the NTP server, but it wasn't syncing. After a bit of a fight, using information from ONTAP 9 - time server rejected as unreliable - NetApp Knowledge Base. I did manage to get the NetApp to sync to the domain controller. 1 month later, go to fix the time skew. Domain controller: Time skew as expected NetApp: Time is still correct I can only surmise that this means that the NetApp is not continuously syncing with the Domain Controller. It got the time once and then just did its own thing. How can I force the NetApp to sync more often?
... 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
Hello, In the past, we relied on McAfee & the antivirus connector to get vscan to work for our filers, but McAfee was retired and replaced with Trellix and i'm having difficulty getting that to work with vscan again. Please advise! Trellix is fully downloaded, and it's been given the IP for our machine but that's about it. I'm not sure how to proceed from here
... View more