Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • https://kb.netapp.com/Legacy/AltaVault/RFSD_process_crashes_with_the_error_KeyValueStore__DbError
      Applies to AltaVault Issue RFSD process crashes with the error KeyValueStore::DbError Manually restarting the optimization service fails. Appliance health is degraded.
    • https://kb.netapp.com/Legacy/AltaVault/AWS_moving_it_s_default_certificates_of_S3_to_Amazon_trust_services
      Applies to AltaVault Amazon Web Services (AWS) ONTAP 9 Issue We have a notification from AWS that it would be moving it’s default certificates of S3 to Amazon trust services, this activity would be ca...Applies to AltaVault Amazon Web Services (AWS) ONTAP 9 Issue We have a notification from AWS that it would be moving it’s default certificates of S3 to Amazon trust services, this activity would be carried out by AWS from March 2021. Since we are utilizing NetApp through which the data is pushed to S3 Glacier, we need to have a confirmation from NetApp that there would not be any breakage in the service flow.
    • https://kb.netapp.com/Legacy/AltaVault/How_to_collect_initial_system_information_sysdump_on_AltaVault
      Applies to AVA400 AVA800 AVA-v Description If you are experiencing a problem with your AltaVault, please send a system dump (sysdump) to help NetApp Support diagnose the issue.
    • https://kb.netapp.com/Legacy/AltaVault/How_to_change_TLS_version_running_on_AltaVault
      Applies to All physical & virtual AltaVault appliances The AVA supports TLSv1, TLSv1.1 and TLSv2. The CLI syntax to change the version of TLS enabled on the AVA is: Syntax [no] web ssl protocol {tlsv1...Applies to All physical & virtual AltaVault appliances The AVA supports TLSv1, TLSv1.1 and TLSv2. The CLI syntax to change the version of TLS enabled on the AVA is: Syntax [no] web ssl protocol {tlsv1 | tlsv1.1 | tlsv1.2} Usage - the no command option disables this setting ::> configuration terminal (config) # web ssl protocol tlsv1 Warning: TLS 1.0 is considered insecure. It is advisable to allow only TLS 1.1 or TLS 1.2 Command-Line Reference Guide found on page 94 of the CLI guide.
    • https://kb.netapp.com/Legacy/AltaVault/Virtual_AltaVault_storage_optimization_service_fails_with_std__bad_alloc
      Jan 26 05:21:55 localhost pm[1742]: [pm.ERR]: Output from rfsd: terminate called after throwing an instance of 'std::bad_alloc' Jan 26 05:21:55 localhost pm[1742]: [pm.ERR]: Output from rfsd: what(): ...Jan 26 05:21:55 localhost pm[1742]: [pm.ERR]: Output from rfsd: terminate called after throwing an instance of 'std::bad_alloc' Jan 26 05:21:55 localhost pm[1742]: [pm.ERR]: Output from rfsd: what(): std::bad_alloc Jan 26 05:21:55 localhost pm[1742]: [pm.ERR]: Output from rfsd: /opt/rbt/bin/rfsd STACK TRACE: #0 0x00ae623d in _ZN6Signal11handle_trapEiP9siginfo_tPv at /opt/rbt/bin/rfsd 0x400000+0x006e623d
    • https://kb.netapp.com/Legacy/AltaVault/How_does_AltaVault_work_with_Amazon_Glacier_FAQ
      After data has been written to Amazon Glacier it is stored in the S3 cloud for a period of 24 hours before it is moved to Amazon Glacier. The Expedited retrieval method may not be available if the AWS...After data has been written to Amazon Glacier it is stored in the S3 cloud for a period of 24 hours before it is moved to Amazon Glacier. The Expedited retrieval method may not be available if the AWS activity is high and the resources to perform the operation are not available. The local cache of data in the AltaVault datastore can help avoid the retrieval of data from Glacier.