Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 18 results
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/ONTAP_upgrade_fails_aes128_gcm_and_aes256_gcm_are_not_supported_when_SSL_FIPS_mode_is_enabled
      ONTAP upgrade with FIPS enabled Cluster::*>system node upgrade-revert show -node Clustern1 Status Message: The upgrade aborted. Contact support personnel for the upgrade repair procedure. Vers Phase S...ONTAP upgrade with FIPS enabled Cluster::*>system node upgrade-revert show -node Clustern1 Status Message: The upgrade aborted. Contact support personnel for the upgrade repair procedure. Vers Phase Status Upgrade Phase Status Message 700 pre-root applied No upgrade is required for this phase. 700 post-apps aborted Cipher(s) "aes128-gcm" and "aes256-gcm" are not supported when SSL FIPS mode is enabled. Clustern1 600 post-apps 637 mgwd aborted sshd config Maxauthtries Upgrade Revert Task
    • https://kb.netapp.com/on-prem/ontap/DM/System_Manager/SM-KBs/System_Manager_Cluster_Guided_Setup_Templates
      Applies to ONTAP 9.7 and earlier System Manager 9.7 and earlier Description System Manager (up to and including the 9.7 release) provides a Guided Setup feature that can use a pre-populated template f...Applies to ONTAP 9.7 and earlier System Manager 9.7 and earlier Description System Manager (up to and including the 9.7 release) provides a Guided Setup feature that can use a pre-populated template file. Set up a cluster by using the template file in System Manager - ONTAP 9.7 and earlier Completed template files used in the cluster setup may be retained for setup/configuration documentation purposes.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapLock/SnapLock-KBs/ONTAP_9.3P4_and_later_require_IBM_Spectrum_Protect_8.1.7_and_later_for_SnapLock_feature
      Applies to ONTAP 9.3P4 and later IBM Spectrum Protect (TSM) SnapLock Issue SnapLock backups fail during the verification of SnapLock volume
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_access_CIFS_shares_due_to_SID_lookup_failed_error
      Unable to access the CIFS shares. A SID lookup fails for the respective domain user: [     4] Could not find Windows SID 'S-1-5-21-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxx' **[     5] FAILURE: SID lookup...Unable to access the CIFS shares. A SID lookup fails for the respective domain user: [     4] Could not find Windows SID 'S-1-5-21-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxx' **[     5] FAILURE: SID lookup failed Error: Lookup of CIFS account SID procedure failed [  2046] Could not find Windows SID 'S-1-5-21-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxx' **[  2046] FAILURE: SID lookup failed Lookup of CIFS account SID procedure succeeded
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_enable_the_equivalent_of_all_squash_in_clustered_Data_ONTAP
      Applies to ONTAP 9 Description The process of Mapping all incoming UIDs in NFS requests to a defined UID is called either squash_all or all_squash
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_are_FlexGroup_Inodes_calculated_after_increasing_the_limits
      Applies to ONTAP 9.2 The inode count limits are given per constituent volume as shown in table 9 (page 45) from the NetApp FlexGroup Volume Best Practices and Implementation Guide This table details t...Applies to ONTAP 9.2 The inode count limits are given per constituent volume as shown in table 9 (page 45) from the NetApp FlexGroup Volume Best Practices and Implementation Guide This table details the default inode counts based on each constituent volume size The table shows that for volume size greater than 1TB the default inode count limit for each volume is 21,251,126 inodes To obtain the current inode count the command df -i can be run from the nodeshell of each node in the cluster
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/cifs_share_show_volume_reports_a_partial_list_of_shares
      Applies to ONTAP 9.3 CIFS Share Volume Issue The command cifs share show -volume <Volume Name> doesn't give a full list of the shares hosted in the specified volume.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Is_ONTAPs_Secure_Multi_Tenancy_SMT_capability_certified
      ONTAP provides this capability by logically separating SVMs using IP Spaces so that inbound and outbound network communication intended for an SVM is not accessible from another SVM on the same storag...ONTAP provides this capability by logically separating SVMs using IP Spaces so that inbound and outbound network communication intended for an SVM is not accessible from another SVM on the same storage platform or within the ONTAP cluster. In addition, a third-party audit that validates ONTAP SVM having an SMT capability can be found in TR-4512: NetApp Secure Multi-Tenancy (SMT) Validation Report.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/NetApp_Volume_Encryption_NVE_considerations_with_SnapMirror_relationships_and_SnapLock_volumes
      Applies to ONTAP 9.7 and earlier ONTAP 9.8 and later NetApp Volume Encryption (NVE) SnapLock SnapMirror Description NetApp Volume Encryption (NVE) considerations with SnapMirror relationships and Snap...Applies to ONTAP 9.7 and earlier ONTAP 9.8 and later NetApp Volume Encryption (NVE) SnapLock SnapMirror Description NetApp Volume Encryption (NVE) considerations with SnapMirror relationships and SnapLock volumes
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Snapshots_-_changing_the_snapshot_policy_may_result_in_losing_snapshots_in_the_next_scheduled_run
      Any Snapshot copies on this volume from the previous policy will not be deleted by this new Snapshot policy. The message implies that all current snapshots will remain, but this is not the case. Once ...Any Snapshot copies on this volume from the previous policy will not be deleted by this new Snapshot policy. The message implies that all current snapshots will remain, but this is not the case. Once the new schedule starts, all snapshots will adhere to the new policy if the naming convention stays the same. If the new retention rule decreases the number of snapshots, then upon the next scheduled run, you will lose the older snapshots based on the new retention limit.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_Snapshots_build_up_on_SnapVault_destination_in_a_Mirror-Vault_cascade
      Applies to ONTAP 9.3 ONTAP 9.4 SnapMirror to SnapVault cascade Issue In a SnapMirror to SnapVault cascade configuration, some volumes may be retaining extra (more than one) "snapmirror" snapshot as se...Applies to ONTAP 9.3 ONTAP 9.4 SnapMirror to SnapVault cascade Issue In a SnapMirror to SnapVault cascade configuration, some volumes may be retaining extra (more than one) "snapmirror" snapshot as seen in the volume snapshot show command on the SnapVault destination. These additional snapshots may cause the SnapVault destination to run out of snapshots prematurely.