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.
Hi, we have a requirement to migrate all CIFS shares currently hosted on a Windows 2012 R2 server to an Azure CVOT cluster. Probably around 10TB of data. I haven't been able to find much via google/this forum, but am wondering if anyone has experience with this or can recommend a tool/documentation. Ideally we'd like to move the hostname to the new vserver as well. We are performing this for an offshoot of our main org so I'm not familiar with the Windows server environment and we had no part in any of the configuration. Currently the plan is to recreate the shares and robocopy the contents.
... View more
Hi, On the A800 there are one network port for e0M and a second for the BMC. With network device-discovery show I see the network neighbors for all ports except for BMC. Is there any possibility to get the BMC port network neighbor as well? Best Regards
... View more
PROBLEM I am configuring (4) NICs on a two-node AF200 9.9.1P6 cluster with LACP, to attach to a pair of Cisco switches (configured with vPC) The (2) Cisco switches are emitting identical LACP System IDs, which is good * Both Cisco switches: 00-23-04-EE-BE-D1 But each of the ONTAP nodes are emitting different LACP System IDs, which is bad * On Node 1, system ID = 02-A0-98-D7-EE-08 * On Node 2, system ID = 02-A0-98-D7-F3-01 CONFIGURE I created the ifgrp as follows: network port ifgrp create -node ontap-n1 -ifgrp a0b -distr-func ip -mode multimode_lacp network port ifgrp create -node ontap-n2 -ifgrp a0b -distr-func ip -mode multimode_lacp network port ifgrp add-port -node ontap-n1 -ifgrp a0b -port e0d network port ifgrp add-port -node ontap-n2 -ifgrp a0b -port e0d network port ifgrp add-port -node ontap-n1 -ifgrp a0b -port e0f network port ifgrp add-port -node ontap-n2 -ifgrp a0b -port e0f ontap-n1::> network port show -ifgrp-port a0b Node: ontap-n1 Speed(Mbps) Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- e0d Default - up 1500 1000/10000 healthy e0f Default - up 1500 1000/10000 healthy Node: ontap-n2 Speed(Mbps) Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- e0d Default - up 1500 auto/10000 healthy e0f Default - up 1500 auto/10000 healthy 4 entries were displayed. ontap-n1::> IFCONFIG -V OUTPUT Node 1: ontap-n1 a0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 [...] laggport: e0f flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3d<ACTIVITY,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING> [(8000,02-A0-98-D7-EE-08,0032,8000,0007), (7F9B,00-23-04-EE-BE-D1,8005,8000,0121)] input/output LACPDUs: 189 / 145043 laggport: e0d flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3d<ACTIVITY,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING> [(8000,02-A0-98-D7-EE-08,0032,8000,0009), (7F9B,00-23-04-EE-BE-D1,8005,8000,4109)] input/output LACPDUs: 218 / 145072 Node 2: ontap-n2 a0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 [...] laggport: e0f flags=0<> state=d<ACTIVITY,AGGREGATION,SYNC> [(8000,02-A0-98-D7-F3-01,0032,8000,0007), (7F9B,00-23-04-EE-BE-D1,8005,8000,0125)] input/output LACPDUs: 124 / 144983 laggport: e0d flags=0<> state=d<ACTIVITY,AGGREGATION,SYNC> [(8000,02-A0-98-D7-F3-01,0032,8000,0009), (7F9B,00-23-04-EE-BE-D1,8005,8000,410A)] I am referring to the following KB article to interpret ifconfig output: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_Troubleshoot_LACP_Issues_with_ifconfig_-v_in_ONTAP_9.2?mt-view=f1 QUESTION What am I missing here? Is there something about the 'ifgrp' creation that I have forgotten? --sk Stuart Kendrick
... View more
Hello community, we have a problem that we are noticing now for the first time. We are currently using ONTAP 9.8P11 on FAS2750. Our network administrators would like to use port 636 for communication with the DNS. A newly created CIFS-SVM - so far without productive use - connects to DNS via port 636 (-use-ldaps-for-ad-ldap is set o true / Root CA was createtd before) when it is accessed for the first time. All further access - although we don't even know why this is happening (there are no accesses from CIFS clients yet!) - are again taking place via port 389? Why? The parameters for the SVM are set as follows: FAS27DX1::> vserver cifs security show -vserver SVM_xxxxx Vserver: SVM_xxxxx Kerberos Clock Skew: 5 minutes Kerberos Ticket Age: 10 hours Kerberos Renewal Age: 7 days Kerberos KDC Timeout: 3 seconds Is Signing Required: true Is Password Complexity Required: true Use start_tls for AD LDAP connection: false Is AES Encryption Enabled: false LM Compatibility Level: lm-ntlm-ntlmv2-krb Is SMB Encryption Required: false Client Session Security: none SMB1 Enabled for DC Connections: false SMB2 Enabled for DC Connections: system-default LDAP Referral Enabled For AD LDAP connections: false Use LDAPS for AD LDAP connection: true Encryption is required for DC Connections: false FASxxxxx::> Can anyone explain this behavior? Why is only the first access via port 636 and the others via 389? What is to be done so that only port 636 is used? Why is there access to the DNS at all if the SVM is not yet productive? (our networkers have determined that this behavior probably occurs every 4 hours - See also graphic "ADROOT-LOG.jpg".). I am grateful for any help. Best regards Michael
... View more
