Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 33 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Can_a_CIFS_server_be_created_in_ONTAP_without_joining_the_CIFS_server_to_a_domain
      ​ ​ ​ Applies to ONTAP 9 Data ONTAP 8 Answer This functionality is supported in ONTAP 9 and above. In 8.3.2 and below, a CIFS server must be joined to a domain. It's not possible to perform a CIFS cre...​ ​ ​ Applies to ONTAP 9 Data ONTAP 8 Answer This functionality is supported in ONTAP 9 and above. In 8.3.2 and below, a CIFS server must be joined to a domain. It's not possible to perform a CIFS create for a workgroup. Additional Information Set up an SMB server in a workgroup overview (netapp.com)
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Data_ONTAP_8__Where_are_EMS_and_messages_log_files_written_in_Data_ONTAP_8_0
      Clustered Data ONTAP 8 Data ONTAP 8 7-mode Messages and EMS log files in Data ONTAP 8.0: Data ONTAP 8.0 7-Mode: EMS_decode+dblade_syslog => old messages file (/etc/messages symlink with /etc/log/messa...Clustered Data ONTAP 8 Data ONTAP 8 7-mode Messages and EMS log files in Data ONTAP 8.0: Data ONTAP 8.0 7-Mode: EMS_decode+dblade_syslog => old messages file (/etc/messages symlink with /etc/log/messages) mhost messages => mhost messages file (/etc/log/mlog/messages.log) EMS only logs => ems log file (/etc/log/ems) Data ONTAP 8.0 Cluster-Mode: EMS+mhost messages => mhost messages file (/mroot/etc/log/mlog/messages.log) EMS only logs => ems log file (/mroot/etc/log/ems)
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_server_create_fails_with_error_OU_not_found_for_ONTAP_9
      Applies to ONTAP 9 Data ONTAP 8 Issue CIFS server create fails with the following error: Failed to create the Active Directory machine account "TEST1". Reason: SecD Error: ou not found FAILURE: Specif...Applies to ONTAP 9 Data ONTAP 8 Issue CIFS server create fails with the following error: Failed to create the Active Directory machine account "TEST1". Reason: SecD Error: ou not found FAILURE: Specified OU ** 'OU=Storage,OU=Servers,DC=NETAPP,DC=COM' does ** not exist in NETAPP.COM . (Error: 13001)
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/During_periods_of_high_traffic_what_is_an_acceptable_percentage_of_discarded_packets_in_ONTAP
      Applies to ONTAP 9 Data ONTAP 8 Data ONTAP operating in 7-Mode Answer Generally, discarded packets below 0.1% of the total traffic should not substantially affect service. Additional Information A hig...Applies to ONTAP 9 Data ONTAP 8 Data ONTAP operating in 7-Mode Answer Generally, discarded packets below 0.1% of the total traffic should not substantially affect service. Additional Information A high volume of traffic can lead bus overruns causing some packets to be discarded. This does not always have a noticeable impact on the environment. More information can be found in our KB article on Troubleshooting Ethernet Network Ports in ONTAP using ifstat. Why does packet loss impact performance?
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Microsoft_Office_suite_temp_files_remain_using_SMB_shares
      Microsoft Application Suite Creation of Microsoft application temp files on storage share can have an impact on the temp file mechanism. It has been seen that at times, while using Microsoft Office wi...Microsoft Application Suite Creation of Microsoft application temp files on storage share can have an impact on the temp file mechanism. It has been seen that at times, while using Microsoft Office with files saved on SMB shares, can lead to the creating of multiple temp files or the Original file is gone but the temp file remains To explain why the temp files are created initially, while working with Microsoft Office, please refer to this Microsoft article:
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Access_denied_error_seen_by_Windows_clients_as_ONTAP_maps_users_to_pcuser_instead_of_the_appropriate_UNIX_user
      Windows users get mapped to the default unix user (pcuser) instead of the appropriate UNIX user Verify whether the expected UNIX user's credentials (Ex: user1 for DOMAIN\user1) are resolved by the SVM...Windows users get mapped to the default unix user (pcuser) instead of the appropriate UNIX user Verify whether the expected UNIX user's credentials (Ex: user1 for DOMAIN\user1) are resolved by the SVM Error: command failed: Failed to resolve user name to a UNIX ID. If the error states "user not found", check which name services are being used for user lookup If ns-switch only lists "files", then the UNIX user must be created locally, if the user is not present in unix-user show output
    • https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/How_to_configure_VMware_vSphere_6.x_on_Data_ONTAP_8.x
      Applies to VMware vSphere 6.x Data ONTAP 8.x Description This article provides the following information for configurations using VMware vSphere 6.x on Data ONTAP 8.x: The configuration parameters tha...Applies to VMware vSphere 6.x Data ONTAP 8.x Description This article provides the following information for configurations using VMware vSphere 6.x on Data ONTAP 8.x: The configuration parameters that meet the best practices guidelines. An example of how to set up a configuration using the best practices recommendations.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_determine_if_a_Windows_Domain_Controller_is_a_suitable_NTP_server_for_Data_ONTAP_8_and_later
      Data ONTAP 8 and later This article describes the procedure on how to determine if a Windows Domain Controller is a suitable NTP server for Data ONTAP 8. Data ONTAP 8 uses NTP for time synchronization...Data ONTAP 8 and later This article describes the procedure on how to determine if a Windows Domain Controller is a suitable NTP server for Data ONTAP 8. Data ONTAP 8 uses NTP for time synchronization. It requires a more accurate time source than that provided by Windows DC by default (10 seconds). Therefore, using Windows DCs, Data ONTAP 8 loses time synchronization. If the time difference between the storage system and the DC is greater than 5 minutes, a CIFS authentication failure will occur.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_enable_or_disable_I2P_on_a_volume
      Applies to ONTAP 9 Data ONTAP 8 Description Inode to pathname is a per volume optional WAFL facility, enabled by default, that provides the ability to map an inode number and volume specification to a...Applies to ONTAP 9 Data ONTAP 8 Description Inode to pathname is a per volume optional WAFL facility, enabled by default, that provides the ability to map an inode number and volume specification to all filer relative pathnames that refer to the inode. The Inode to pathname feature can be turned on or off by following the steps below.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Permission_denied_for_root_via_NFS_to_UNIX_vol_when_using_chown_or_chmod
      Security Style UNIX Commands chown or chmod fail as root user on an NFS export of a volume or qtree with UNIX security style: permission denied Volume or qtree security style, or effective security st...Security Style UNIX Commands chown or chmod fail as root user on an NFS export of a volume or qtree with UNIX security style: permission denied Volume or qtree security style, or effective security style, is UNIX. Note: This is not applicable to NTFS security style. Failing to change permissions or ownership is expected for unix users accessing ntfs security style volumes The vserver export-policy rule show output displays superuser policy type is set to none.
    • https://kb.netapp.com/Legacy/ONTAP/7Mode/How_to_set_up_and_troubleshoot_Widelinks_on_a_Netapp_7-mode_Storage_Controller
      The following examples illustrate how to create a symlink from volume to qtree on the same filer, and from volume to volume on different filers. Share the qtree for the CIFS client, turn on support fo...The following examples illustrate how to create a symlink from volume to qtree on the same filer, and from volume to volume on different filers. Share the qtree for the CIFS client, turn on support for widelinks in the share which will contain the symlink: Use a UNIX client to create the target file and to create the symlink which will be used to point to it.