I'm trying to setup my svm server to talk Kerberos only (v9.15). My environment is setup to use aes-128 and aes-256 encryption and svm server has been joined to the domain. However, when I run command ...-lm-compatibility-level krb, ALL of my CIFS shares become inaccessible, I get re-prompted to enter my AD credentials and despite entering my credentials correctly, I never get in. I end up reverting back to ...-lm-compatibility-level ntlmv2-krb. Has anyone been able to set their CIFS shares to run krb traffic only?  Added context: CIFS shares need to be visible to Windows Server 2022 server. ... View more

Hello, we trying to mount a NetApp CIFS share on SLES 11 with SMB 2.1 as follows: Mount -v -o auto, username = xxxxxx, password = xxxxxx, workgroup = XXXXXX, uid = hostftp, gid = users, vers = 2.1, noserverino // <server> / <shared name> / <local_folder> / <local_subserver> Mount and access work, but the mount seems to be done with SMB 1 only: CLUSTER ::> vserver cifs sessionshow -vserver SVM_XXXXXXX -fields shares, windows-user, idle-time, session-id, address, protocol-version, user-type, files Node vserver session-id connection-id address windows-user shares files idle-time protocol-version user-type -------- ------------ ------------------------------------------------ ------- --------------- ------ ----- --------- -------- -------- ----------- NodeXX SVM_XXXXXXX 1 932666088 NNN.18.121.131 DOMAIN \ hostftp 2 0 1m 29s SMB1 domain-user : NodeXX SVM_XXXXXXX 12261331460493166545 932952775 NNN.NN.1.187 DOMAIN \ VNNNN1 2 3 21m 47s SMB2_1 domain-user NodeXX SVM_XXXXXXX 12261331460493203961 932990989 NNN.NN.187.108 DOMAIN \ VNNNN2 1 9 5s SMB2_1 domain-user NodeXX SVM_XXXXXXX 12261331460493216289 933003440 NNN.NN.84.10 DOMAIN \ vNNNN3 1 9 1m 56s SMB2_1 domain-user :   Mounting CIFS-shares using SMB 2.1  works well on Windows-Clients (see above - windows-user: DOMAIN \ VNNNNx ) (System FAS8040 running ONTAP 9.1P3) Any idea? Thanks and best regards Michael ... View more

Hello,   I have a FAS2552 with Ontap 9.8 SVM for NFS. Auth: Unix System Hosts have Root acces (Super user) Tested (SSH/ESX) by creating a folder and file on the NFS datastore   I can Copy a vm to the datastore, register VM and i can start it. I cannot do a storage migration from other NFS store (QNAP):  Unable to load configuration file *VMX 13 (Permission denied). I cannot create a clone from other VM. Same error. And i cannot create a new VM, also with the same error. It looks like FP Policy, but when this is what i see when i check it: SCL01::> vserver fpolicy show This table is currently empty. Could there be something else blocking it?   ... View more

Hello all,   Long story short.   The issue is that Logstash is duplicating logs after application restarts due to PVCs being mounted with different minor device versions, causing Logstash to mistakenly treat the same log files as different. Having said that, I’d like to know if it's normal for the 'minor device number' of an NFS 4.0 volume to change when it’s mounted multiple times.   This appears to be a known issue when working with Network File Systems, as outlined in the Elastic documentation I found online, this happens because NFS can present different minor device versions, which Logstash interprets as different file systems, leading to log duplication: https://www.elastic.co/docs/reference/logstash/plugins/plugins-inputs-file#_reading_from_remote_network_volumes   If any of you folks have a second opinion on this, I'd love to hear it.   Thank you very much,   Joel. ... View more