Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • DISK REDUNDANCY FAILED after shelf expansion
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/DISK_REDUNDANCY_FAILED_after_shelf_expansion
      11/19/2021 19:22:48 cluster-node01 ALERT hm.alert.raised: Alert Id = SinglePathToDiskShelf_Alert , Alerting Resource = 13650257700721330768 raised by monitor node-connect 11/19/2021 19:22:48 cluster-n...11/19/2021 19:22:48 cluster-node01 ALERT hm.alert.raised: Alert Id = SinglePathToDiskShelf_Alert , Alerting Resource = 13650257700721330768 raised by monitor node-connect 11/19/2021 19:22:48 cluster-node01 ALERT hm.alert.raised: Alert Id = SinglePathToDiskShelf_Alert , Alerting Resource = 9455720896314018384 raised by monitor node-connect
    • E-Series How to map LSI/Avago based SAS adapters in Auto port mode
      https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E_Series_How_to_map_LSI_Avago_based_SAS_adapters_in_Auto_port_mode
      SAS based hosts can lose the data path to the array due to SAS ports to change and to come up in different order. Each SAS port exist of four single ports, each port has it's own SAS address. SAS HBA'...SAS based hosts can lose the data path to the array due to SAS ports to change and to come up in different order. Each SAS port exist of four single ports, each port has it's own SAS address. SAS HBA's should operate in Wide mode by default but native SAS LSI/Avago Host Bus Adapters (HBA) operate in default Auto port mode instead. This causes indicator to host mapping to fail as the mapping is based on the SAS port address.
    • Higher than expected SSD latency due to 6Gb SAS shelves and cables
      https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Higher_than_expected_SSD_latency_due_to_6Gb_SAS_shelves_and_cables
      cluster1::> qos statistics volume latency show -vserver svm1 -volume vol1 Workload ID Latency Network Cluster Data Disk QoS Max QoS Min NVRAM --------------- ------ ---------- ---------- ---------- --...cluster1::> qos statistics volume latency show -vserver svm1 -volume vol1 Workload ID Latency Network Cluster Data Disk QoS Max QoS Min NVRAM --------------- ------ ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- -total- - 4.71ms 185.00us 7.00us 468.00us 4.04ms 0ms 0ms 11.00us vol1-wid32140 32140 22.22ms 86.00us 125.00us 904.00us 21.11ms 0ms 0ms 1.00us -total- - 4.58ms 253.00us 7.00us 991.00us 3.32ms 0ms 0ms 11.00us vol1-wid32140 32140 29.69ms 90.00us 162…
    • ONTAP - How to re-enable a disabled SAS port
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/ONTAP_-_How_to_re-enable_a_disabled_SAS_port
      Applies to ONTAP 9 Description This procedure enables a SAS port that has been disabled The port may have been disabled during troubleshooting to stop port flapping The disabled port will carry over a...Applies to ONTAP 9 Description This procedure enables a SAS port that has been disabled The port may have been disabled during troubleshooting to stop port flapping The disabled port will carry over across reboots and SAS card swaps The port will show offline both at the Cluster prompt and in Maintenance Mode
    • System is in mixed path due to fault seen on SAS HBA
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/System_is_in_mixed_path_due_to_fault_seen_on_SAS_HBA
      Applies to NetApp AFF and FAS systems ONTAP 9 Issue Drives are missing a path to the node due to a faulty port on a SAS card Shelf stack is not seen through IO Module A/B and drives connected through ...Applies to NetApp AFF and FAS systems ONTAP 9 Issue Drives are missing a path to the node due to a faulty port on a SAS card Shelf stack is not seen through IO Module A/B and drives connected through IO Modules A/B are not seen by the Node, refer to the additional information section