Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/FlexArray_duplicate_disk_names_after_array_and_prefix_renaming
      During/after array/prefix rename operation the system shows duplicate disk name for different array LUNs: When migrating legacy storage using FLI to NetApp may observer a duplicate disk name Disk name...During/after array/prefix rename operation the system shows duplicate disk name for different array LUNs: When migrating legacy storage using FLI to NetApp may observer a duplicate disk name Disk names with the prefix from one of the array are missing ::> disk show array_1* Disk Size Shelf Bay Type Type Name Owner array_1.1 28.44GB - 0 SSD aggregate cluster1-01 array_1.2 28.44GB - 1 SSD aggregate cluster1-01 array_1.3 28.44GB - 2 SSD aggregate cluster1-01
    • https://kb.netapp.com/data-mgmt/SMI-S/SMI-S_KBs/Failed_to_add_a_E-series_to_Netapp_SMI-S_with_error_HTTP_POST_302
      Applies to Netapp SMI-S provider 5.2.6 Netapp Santricity SMI-S provider E-series storage system Issue The smis add command fails with error CIM_ERR_FAILED: Filer return: HTTP POST - failed, status cod...Applies to Netapp SMI-S provider 5.2.6 Netapp Santricity SMI-S provider E-series storage system Issue The smis add command fails with error CIM_ERR_FAILED: Filer return: HTTP POST - failed, status code = 302 - with storage system <ip>
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/How_to_perform_an_offline_upgrade_of_backend_array_firmware_for_FlexArray
      Applies to NetApp E-Series ONTAP 9 FlexArray V-Series (Legacy) Description Array storage is virtualized through the FlexArray (V-Series) license by Data ONTAP with different levels of interoperability...Applies to NetApp E-Series ONTAP 9 FlexArray V-Series (Legacy) Description Array storage is virtualized through the FlexArray (V-Series) license by Data ONTAP with different levels of interoperability Explicit support (ALUA/TPGS) for non-disruptive backend firmware upgrades is not always possible without risk of a panic on the Data ONTAP due to loss of connectivity
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Cluster_peering_reports_Pending_availability
      This article provides the solution when a cluster peer reports Pending availability in the cluster peer show command output
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Tunable_parameters_in_ONTAP_9.0_for_reliably_handling_backend_disruptions_in_FlexArray_Virtualization_environment
      Applies to Description Beginning with ONTAP 9.0, FlexArray Virtualization (V-Series) includes resiliency enhancements to reliably handle disruptions caused by back-end path failures, for example, link...Applies to Description Beginning with ONTAP 9.0, FlexArray Virtualization (V-Series) includes resiliency enhancements to reliably handle disruptions caused by back-end path failures, for example, link and switch failures. The resiliency enhancements include the following: Consistent I/O failover timing in case of path failures Temporary suspension of I/O for a tunable period of time in case of all-path fail conditions Automatic path quiescence in case of intermittent path failures