Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 110 results
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/FabricPool_not_tiering_data_with_aborted-nospace_error
      FabricPool stopped tiering the data to cloud tier. Running the "volume object-store tiering show" shows aborted-nospace cluster01::*> vol object-store tiering show -volume vol1 -vserver svm1 Previous ...FabricPool stopped tiering the data to cloud tier. Running the "volume object-store tiering show" shows aborted-nospace cluster01::*> vol object-store tiering show -volume vol1 -vserver svm1 Previous Run Status: aborted-nospace Time Scanner Last Finished: Wed Feb 05 09:52:51 2025 Time Waiting Scan will be scheduled: - Tiering Policy: auto space error code encountered in last scan: - And when running 'storage aggregate object-store show' shows "is-tiering-allowed' to 'false'
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Can_I_convert_a_Flexvol_to_FlexGroup_without_rewarming_the_tiered_data
      ::> volume show-footprint myvol Vserver : svm1 Volume : myvol Feature Used Used% -------------------------------- ---------- ----- Volume Data Footprint 14.09GB 0% Footprint in Performance Tier 268.5M...::> volume show-footprint myvol Vserver : svm1 Volume : myvol Feature Used Used% -------------------------------- ---------- ----- Volume Data Footprint 14.09GB 0% Footprint in Performance Tier 268.5MB 2% Footprint in <your storage Tier> 13.84GB 98% Volume Guarantee 0B 0% Flexible Volume Metadata 683.9MB 0% Deduplication 61.40MB 0% Cross Volume Deduplication 143.0MB 0% Delayed Frees 6.09MB 0% Total Footprint 14.97GB 0%
    • 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."
    • https://kb.netapp.com/on-prem/ontap/DM/FabricPool/FabricPool-KBs/Cloud_Tier_not_available_after_StorageGRID_certificate_expired_in_ONTAP
      2021-08-19T16:09:08Z 12420713417701232 [4:0] OSC_ERR: logFailedCmd:367 Stats of PUT Cmd ID:128, wait 127049us, start-send 127167us, 1stbyte 0us, 1st-lastbyte 0us 2021-08-19T16:09:09Z 12420715329112830...2021-08-19T16:09:08Z 12420713417701232 [4:0] OSC_ERR: logFailedCmd:367 Stats of PUT Cmd ID:128, wait 127049us, start-send 127167us, 1stbyte 0us, 1st-lastbyte 0us 2021-08-19T16:09:09Z 12420715329112830 [15:0] OSC_ERR: logFailedCmd:367 Stats of PUT Cmd ID:128, wait 124031us, start-send 124137us, 1stbyte 0us, 1st-lastbyte 0us 2021-08-19T16:09:10Z 12420717245485368 [13:0] OSC_ERR: logFailedCmd:367 Stats of PUT Cmd ID:128, wait 123929us, start-send 124031us, 1stbyte 0us, 1st-lastbyte 0us
    • 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
    • https://kb.netapp.com/Cloud/BlueXP/Cloud_Tiering/Add_Cloud_Tier_only_shows_StorageGRID_and_ONTAP_S3_and_the_rest_are_greyed_out
      Applies to FabricPool NetApp Cloud Tiering Issue System Manager "Add Cloud Tier" only shows the possibility of "StorageGRID" and "ONTAP S3", the rest of the options are greyed-out, including "Others" ...Applies to FabricPool NetApp Cloud Tiering Issue System Manager "Add Cloud Tier" only shows the possibility of "StorageGRID" and "ONTAP S3", the rest of the options are greyed-out, including "Others" The command "storage aggregate object-store config create" also only allows the provider-types "SGWS" and "ONTAP_S3"
    • 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.
    • https://kb.netapp.com/hybrid/StorageGRID/Alerts/FabricPool_gets_object_store_unavailable__Unable_to_connect_to_the_object_store_Bucket_from_node_Reason
      object.store.unavailable: Unable to connect to the object store "S3Bucket" from node. 2021-09-20T21:59:05Z 1286494450952600 [0:0] OSC_ERR: logFailedCmd:352 PUT Cmd ID:975 name:"Object" failed with OSC...object.store.unavailable: Unable to connect to the object store "S3Bucket" from node. 2021-09-20T21:59:05Z 1286494450952600 [0:0] OSC_ERR: logFailedCmd:352 PUT Cmd ID:975 name:"Object" failed with OSC error: 109 2021-09-20T21:59:05Z 1286494450955754 [0:0] OSC_ERR: logFailedCmd:368 Stats of PUT Cmd ID:975, wait 0us, start-send 142296us, 1stbyte 77133us, 1st-lastbyte 13us 2021-09-20T21:59:05Z 1286494453372192 [0:0] OSC_ERR: populateErrorResponse:903 Unknown error code from provider: ExceededQuota
    • https://kb.netapp.com/hybrid/StorageGRID/Protocols/18_minutes_delay_between_object-store_going_unavailable_and_available
      Ontap EMS logs will show close to 18 minutes delay between Object Store going unavailable and back to available In the latter situation the total time of Object Store being unavailable is 20 minutes (...Ontap EMS logs will show close to 18 minutes delay between Object Store going unavailable and back to available In the latter situation the total time of Object Store being unavailable is 20 minutes (2 minutes for the first Unavailable message + 18 minutes later for the Available message) Usual behavior is that a HEAD call is made after going unavailable, which unless there is a more serious issue will be successful and the Object Store will be marked Available again with 1-2 seconds.
    • https://kb.netapp.com/hybrid/StorageGRID/Performance/What_are_the_implications_of_setting_DNS_TTL_with_FabricPool
      Affects of TTL with DNS RR Group TTL weights the amount of time before the next DNS record is resolved After 4 hours Host2 handles all IO for the next 4 hours Dictates how long the DNS query is cached...Affects of TTL with DNS RR Group TTL weights the amount of time before the next DNS record is resolved After 4 hours Host2 handles all IO for the next 4 hours Dictates how long the DNS query is cached for the specified record DNS RR is used to create High Availability Gateway Nodes Gateway nodes establish HTTP sessions to send S3 operations to the Storage Nodes TTL values can cause a single Gateway Node to establish all sessions to serve IO Uses Virtual IPs (VIPs) to associate to the Active Node
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Failure_error_message__Aborted_Insufficient_storage_space_Ensure_that_there_is_enough_space_in_the_volume
      Applies to FabricPool Encryption When trying encrypt a non-encrypted fabricpool volume or trying to rekey a fabricpool volume that has tiered data, following error was received: ERROR enc.operation.ab...Applies to FabricPool Encryption When trying encrypt a non-encrypted fabricpool volume or trying to rekey a fabricpool volume that has tiered data, following error was received: ERROR enc.operation.aborted: Conversion to encryption scan is aborted in the volume 'data_vol' (aggr 'fp_aggr1'). Reason: Insufficent storage space. sj-clus-01::> vol encryption conversion show Vserver Volume Start Time Status data_vol - Aborted. Insufficent storage space. Ensure that there is enough space in the volume.