Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 25 results
    • Initializing snapmirror relationship to an aggregate with FabricPool and destination aggregate fills up
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Initializing_snapmirror_relationship_to_an_aggregate_with_FabricPool_and_destination_aggregate_fills_up
      Applies to ONTAP 9 FabricPool Issue While initializing snapmirror relationship to destination aggregate with Fabricpool and the destination aggregate ran out of space.
    • Adding a Cloud Storage Tiering fails: Wrong port or server is not available
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Tiering/Adding_a_Cloud_Storage_Tiering_fails__Wrong_port_or_server_is_not_available
      Applies to ONTAP 9 Cloud Volume ONTAP (CVO) FabricPool Tiering System Manager Issue When adding cloud storage tier in system manager the following Error is provided: Error: "Cannot verify availability...Applies to ONTAP 9 Cloud Volume ONTAP (CVO) FabricPool Tiering System Manager Issue When adding cloud storage tier in system manager the following Error is provided: Error: "Cannot verify availability of the object storage from <node> Reason: Wrong port or server is not available."
    • Failed to attach aggregate to object store. The volume does not exist
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Failed_to_attach_aggregate_to_object_store._The_volume_does_not_exist
      00000005.0029cec6 084bb9d1 Wed Dec 02 2020 19:33:32 +00:00 [kern_mgwd:info:2242] 0x81f077a00: 8503e80000268a62: ERR: MGWD:aggr_iterator: attach_imp:src/tables/aggr.cc:23288 aggr_iterator::populate_btu...00000005.0029cec6 084bb9d1 Wed Dec 02 2020 19:33:32 +00:00 [kern_mgwd:info:2242] 0x81f077a00: 8503e80000268a62: ERR: MGWD:aggr_iterator: attach_imp:src/tables/aggr.cc:23288 aggr_iterator::populate_btuuid() returned error (12:591): "Failed to attach aggregate "aggr2" to object store "StorageAccount". Reason: The volume does not exist for the operation.". aggrName=aggr2, aggregate_uuid=97618eda-92f6-4c3c-9d2f-4083455f5454, filer_name=NODE-01.
    • Files can be accessed from a disconnected object store for tiering-policy all
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Files_can_be_accessed_from_a_disconnected_object_store_for_tiering-policy_all
      cluster2::> net in show -role intercluster (network interface show) Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ---------- ----------...cluster2::> net in show -role intercluster (network interface show) Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ---------- ---------- ------------------ ------------- ------- ---- cluster2 intercluster1 down/down 192.168.0.154/24 cluster2-01 e0a true
    • How to adjust the IDR cooling period in ONTAP 9.8 and higher
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Tiering/How_to_adjust_the_IDR_cooling_period_in_ONTAP_9.8_and_higher
      Applies to ONTAP 9.8 and higher Inactive Data Reporting (IDR) FabricPool Tiering Description Prior to ONTAP 9.8, the default tiering minimum cooling days was 31 and could not be adjusted Starting in O...Applies to ONTAP 9.8 and higher Inactive Data Reporting (IDR) FabricPool Tiering Description Prior to ONTAP 9.8, the default tiering minimum cooling days was 31 and could not be adjusted Starting in ONTAP 9.8, this value can be adjusted for auto and snapshot-only tiering policies
    • How does FabricPool inactive data reporting work?
      https://kb.netapp.com/on-prem/ontap/DM/FabricPool/FabricPool-KBs/How_does_FabricPool_inactive_data_reporting_work
      Once enabled, Inactive Data Reporting (IDR) monitors the underlying data access across a fixed 31-day cooling period to determine which data is considered cold or inactive. The performance-tier-inacti...Once enabled, Inactive Data Reporting (IDR) monitors the underlying data access across a fixed 31-day cooling period to determine which data is considered cold or inactive. The performance-tier-inactive-user-data field displays the amount of inactive user data stored in the performance tier that could be tiered out to a cloud tier if the volume is in a FabricPool and for which the auto tiering policy has been specified
    • AIQ Digital Advisor shows all data as Unmonitored Data
      https://kb.netapp.com/data-mgmt/Digital-Advisor-KBs/AIQ_Digital_Advisor_shows_all_Unmonitored_Data
      Applies to ActiveIQ Digital Advisor (AIQDA) ONTAP cluster Cloud Recopmmendations Tiering Issue ActiveIQ Digital Advisor shows all data as Unmonitored Data and gives the reason Inactive Data Reporting ...Applies to ActiveIQ Digital Advisor (AIQDA) ONTAP cluster Cloud Recopmmendations Tiering Issue ActiveIQ Digital Advisor shows all data as Unmonitored Data and gives the reason Inactive Data Reporting Disabled In ONAP the setting enable_auto_cold_data_reporting=on is enabled
    • Object store offline during ifgrp maintenance
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Object_store_offline_during_ifgrp_maintenance
      Applies to ONTAP 9 Issue During interface group (ifgrp) maintenance, object store connectivity is lost on a node with the following error: Wed Jan 27 18:21:15 -0700 [Cluster01-01: OscLowPriThreadPool:...Applies to ONTAP 9 Issue During interface group (ifgrp) maintenance, object store connectivity is lost on a node with the following error: Wed Jan 27 18:21:15 -0700 [Cluster01-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "store1" from node 2e4c8f59-fd6e-11e8-b49b-00a098f67848. Reason: Inter-cluster LIF not configured.
    • High READ Latency from the fabric pool aggregate
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/High_READ_Latency_from_the_fabric_pool_aggregate
      Applies to ONTAP 9.2+ FabricPool Issue Excessive high latency is reported on volumes carved out of aggregates with cloud object Store tiering enabled.
    • Volume tiering very slow in ONTAP 9.8
      https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Volume_tiering_very_slow_in_ONTAP_9.8
      Applies to ONTAP 9.8 FabricPool Issue Volumes not tiering off data, even with Tiering Policy of all
    • Can I disable FabricPool tiering?
      https://kb.netapp.com/on-prem/ontap/DM/FabricPool/FabricPool-KBs/Can_I_disable_FabricPool_tiering
      Applies to ONTAP 9 FabricPool Cloud Tiering The recommended way to stop the tiering is by configuring the tiering-policy to NONE. Setting the tiering policy to NONE will only stop the tiering scanner ...Applies to ONTAP 9 FabricPool Cloud Tiering The recommended way to stop the tiering is by configuring the tiering-policy to NONE. Setting the tiering policy to NONE will only stop the tiering scanner and thus, stop the tiering. However, other operations like volume move, defragger etc will still work the same with the tiering policy set to NONE. To completely stop access and PUTs to cloud tier, contact NetApp Technical Support and refer to this article for the action plan. Additional Information