Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 19 results
    • Direct Attach support for Stretch MetroCluster Configuration with NetApp E-Series array
      https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Direct_Attach_support_for_Stretch_MetroCluster_Configuration_with_NetApp_E-Series_array
      Stretch MetroCluster with both NetApp E-Series Array LUNs and NetApp native disks where NetApp Native Disks are connected via Optical SAS cables. Stretch MetroCluster with both NetApp E-Series Array L...Stretch MetroCluster with both NetApp E-Series Array LUNs and NetApp native disks where NetApp Native Disks are connected via Optical SAS cables. Stretch MetroCluster with both NetApp E-Series Array LUNs and NetApp native disks where NetApp Native Disks are connected via FC to SAS bridges. In a stretch MetroCluster configuration with NetApp E-Series Array LUNs, you must cable each controller's HBA ports to target ports on the corresponding NetApp E-Series Array Controllers.
    • How to identify which disk on a FAS/FlexArray maps to a corresponding E-series volume
      https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/How_to_identify_which_disk_on_a_FAS_FlexArray_maps_to_a_corresponding_E_series_volume
      Applies to • E-series • FlexArray • V-series • FAS Description Some FlexArray setups will have virtual disks which are being presented from a backend storage. The E-series system will present each vol...Applies to • E-series • FlexArray • V-series • FAS Description Some FlexArray setups will have virtual disks which are being presented from a backend storage. The E-series system will present each volume to the FAS system as a disk. In the event troubleshooting is needed against a specific FAS disk and which volume on E-series it corresponds to.
    • Error during FLI: This disk is in a failed state with the outage reason "failed". The Disk needs to be removed and replaced
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Error_during_FLI__This_disk_is_in_a_failed_state_with_the_outage_reason_failed_The_Disk_needs_to_be_removed_and_replaced
      An error occurs during lun import from third-party storage to NetApp: Cluster_1::*> storage disk show -array-name xxxx_xX_x -instance Controller Initiator ID Switch Port Switch Port Acc Use Target Por...An error occurs during lun import from third-party storage to NetApp: Cluster_1::*> storage disk show -array-name xxxx_xX_x -instance Controller Initiator ID Switch Port Switch Port Acc Use Target Port TPGN Speed I/O KB/s IOPS Cluster_1-02 2d 0 zz-zz-zzz-01-01:2-43 zzz-zz-zzz-01:1-23 AO INU 50000975780110c6 7 16 Gb/S 0 0 This disk is in a failed state with the outage reason "failed". The Disk needs to be removed and replaced.
    • FlexArray duplicate disk names after array and prefix renaming
      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
    • Multi disk panic in FlexArray with third-party storage
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Multi_disk_panic_in_FlexArray_with_third-party_storage
      In a Flex Array configuration one or more LUNs missing on all available paths will result in a Multi Disk Panic. Flex Array does not support raid redundancy (raid 4, raidDP, raidTEC) for third party s...In a Flex Array configuration one or more LUNs missing on all available paths will result in a Multi Disk Panic. Flex Array does not support raid redundancy (raid 4, raidDP, raidTEC) for third party storage The HA-partner will not be able to take over if the third party storage is not reachable from the partner Panic string: aggr aggrname: raid volfsm, fatal disk error in RAID group with no parity disk. raid type raid0 in SK process config_thread on release 9.x (C)
    • Flexarry pre-upgrade check reports error "Data ONTAP requires that an array LUN be visible on only one target port for each initiator port"
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Flexarry_pre_upgrade_check_reports_error_Data_ONTAP_requires_that_an_array_LUN_be_visible_on_only_one_target_port_for_each_initiator_port
      Applies to ONTAP 9 FAS System FlexArray Issue During pre-upgrade checks, customer might see below error due to misconfiguration of zoning: "Data ONTAP requires that an array LUN be visible on only one...Applies to ONTAP 9 FAS System FlexArray Issue During pre-upgrade checks, customer might see below error due to misconfiguration of zoning: "Data ONTAP requires that an array LUN be visible on only one target port for each initiator port"
    • Can a FlexArray back-end LUN that is used in an aggregate be replaced with another?
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Can_a_FlexArray_back_end_LUN_that_is_used_in_an_aggregate_be_replaced_with_another
      A FlexArray back-end array LUN that is used in an aggregate cannot be replaced with another LUN Normally, the command storage disk replace can be used to replace a disk used in an aggregate with anoth...A FlexArray back-end array LUN that is used in an aggregate cannot be replaced with another LUN Normally, the command storage disk replace can be used to replace a disk used in an aggregate with another The newly built disk takes the place of the source disk in the aggregate Since there is no redundancy in the aggregate, the command storage disk replace cannot work If LUNs in an aggregate need to be replaced, a more roundabout way is recommended
    • FlexArray back-end LUNs show status Failed
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/FlexArray_back-end_LUNs_show_status_Failed
      FlexArray back-end LUNs show the status as Failed. Node01 failed Error: Takeover failed. Action: Use the "storage failover show-takeover" command to view the cause of takeover failure and the "storage...FlexArray back-end LUNs show the status as Failed. Node01 failed Error: Takeover failed. Action: Use the "storage failover show-takeover" command to view the cause of takeover failure and the "storage failover takeover -ofnode Node Node Status Aggregate Takeover Status To abort the takeover, takeover using the "storage you want to continue the takeover, address the failures and then use the "storage you want to continue with the the failures you can do so by using the "storage failover
    • FlexArray controller reboot after disk failure on E-Series back-end
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FlexArray_controller_reboot_after_disk_failure_on_E-Series_back-end
      Applies to FlexArray/V-Series E-Series ONTAP 9 Issue FAS controller reboots after disk failure on E-Series back-end.
    • FlexArray back-end LUNs show status Failed-Unsupported
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FlexArray_back-end_LUNs_show_status_Failed-Unsupported
      backend-sw3:7.126L0 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L1 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L2 : HITACHI OPEN-V 8801 0.0G...backend-sw3:7.126L0 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L1 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L2 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L3 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L4 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported) backend-sw3:7.126L5 : HITACHI OPEN-V 8801 0.0GB 0B/sect (Failed-Unsupported)
    • FlexArray Multi-Disk panic due to fabric errors and zoning misconfiguration
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FlexArray_Multi-Disk_panic_due_to_fabric_errors_and_zoning_misconfiguration
      Applies to ONTAP 9 FlexArray Issue Switch side single port failure caused port flapping resulting in a Multi-Disk panic at ONTAP Storage FlexArray