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
We upgraded our 2 Clusters from ONTAP 8.3.2 to 9.1 Since upgrading we have noticed a change when trying to access a CIFS share when the user connecting is logged onto a different AD domain to the SVM. The end user no longer get challenged for a user ID and password. Instead because the user ID is the same it tries to use the users credentials including password to connect and after a while the end user gets the following errors System error 64 has occurred. The specified network name is no longer available. If the end user keeps trying to access it, their account on the AD domain that the SVM is on will become locked. However if they specify their credentials including password from the command line, i.e. net use \\CIFS_SVM\share_name /user:{user_id} {password} then it works and they can then access the share. They can also do this from the GUI and it also works. so we have a workaround, but just wondered why the difference between 8.3.2 and 9.1 is it a bug or intentional?
... View more
Hi, Is there a way to know what SMB version is being used for dc connections. I see both SMB1 and SMB2 are enabled at the cluster level for DC connections and the domain controller SMB configuration says the same. How do I know which version of SMB is being used by CIFS sessions. This is required as the new array replacing the old one can use SMB2.0 instead of SMB1.0 for dc connections. Version: ONTAP 9.1P2
... View more
Any idea on how to fix XCP file analytics error: (pg.InternalError) FATAL: password authentication failed for user "central" We have tried everything we can think of, and can not get it to work. When contacting support, they throw KB after KB with no movement towards a solution. Our environment is running RHEL 8.5, 32GB mem, XCP 1.8.
... View more
