Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 21 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/New_Cisco_Nexus_9336C-FX2_cluster_switch_is_unsupported
      Applies to Cisco 9336C-FX2 ONTAP 9.1 - 9.4 ONTAP 9.5P1 - 9.5P15 ONTAP 9.6P1 - 9.6P11 ONTAP 9.7P1 - 9.7P9 Issue Cisco Nexus 9336C-FX2 showing as unsupported: HA Group Notification (Health Monitor proce...Applies to Cisco 9336C-FX2 ONTAP 9.1 - 9.4 ONTAP 9.5P1 - 9.5P15 ONTAP 9.6P1 - 9.6P11 ONTAP 9.7P1 - 9.7P9 Issue Cisco Nexus 9336C-FX2 showing as unsupported: HA Group Notification (Health Monitor process cshm: UnsupportedSwitch_Alert[Switch_Name]) ALERT CSHM-SWITCH-CONFIG.XML autosupport shows the switches as Unsupported Model System health alert for Unsupported cluster switch is detected
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Environmental_Reason_Shutdown_Battery_PCT_capacity_critical
      Emergency shutdown of storage controller with reason 'Battery PCT capacity critical', could be caused due to battery issue.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Health_monitor_alert_SPNotConfiguredAlert
      The system health alert show command shows the below details: Use the "system service-processor network modify" command to configure the network interface of the Service Processor. Use the "system ser...The system health alert show command shows the below details: Use the "system service-processor network modify" command to configure the network interface of the Service Processor. Use the "system service-processor image modify -node cluster-01 -autoupdate true" to configure AutoUpdate feature of the Service Processor. Possible Effect: You might not be able to use the Service Processor to remotely access, monitor, and troubleshoot your storage system.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_diagnose_mixed-path_system_storage_configuration
      Applies to Data ONTAP 8 ONTAP 9 MetroCluster Description This article describes how to diagnose mixed-path system storage configuration As there can be multiple causes, methods to verify and workaroun...Applies to Data ONTAP 8 ONTAP 9 MetroCluster Description This article describes how to diagnose mixed-path system storage configuration As there can be multiple causes, methods to verify and workarounds are listed below
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/DS4246_disk_shelf_status_non-critical_condition
      Mon Jun 21 07:11:51 KST [EMR:ses.status.psInfo:info]: DS4246 (S/N xxxxxxxxxxxxxxx) shelf 3 on channel 0a power supply information for Power supply 3: normal status. Mon Jun 21 07:11:51 KST [PACS:ses.s...Mon Jun 21 07:11:51 KST [EMR:ses.status.psInfo:info]: DS4246 (S/N xxxxxxxxxxxxxxx) shelf 3 on channel 0a power supply information for Power supply 3: normal status. Mon Jun 21 07:11:51 KST [PACS:ses.status.psInfo:info]: DS4246 (S/N xxxxxxxxxxxxxxx) shelf 3 on channel 0b power supply information for Power supply 3: normal status. Shelf 3: XXX XXX XXX XXX XXX XXX XXX 16 XXX XXX XXX 12 11 10 9 8 7 6 5 4 3 2 1 0 Shelf 4: XXX XXX XXX XXX XXX XXX XXX XXX XXX XXX XXX 12 11 10 9 8 7 6 5 4 3 2 1 0
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Single_Path_HA_to_NS224_Shelf
      Applies to ONTAP 9 NS224 Issue Call home alerts for NoPathToNSMA/NoPathToNSMB Single path HA reported Jul 24, 2022 00:38:04 -0700 HA Group Notification (Health Monitor process nchm: NoPathToNSMB_Alert...Applies to ONTAP 9 NS224 Issue Call home alerts for NoPathToNSMA/NoPathToNSMB Single path HA reported Jul 24, 2022 00:38:04 -0700 HA Group Notification (Health Monitor process nchm: NoPathToNSMB_Alert[1234567890]) ALERT
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_read_IFSTAT_counters_on_your_AFF_FAS_systems
      The command is executed from the Nodeshell of each node cluster::> system node run -node <node_name> -command ifstat [ -z ] -a | <interface_name> cluster::> system node run -node node_example> -comman...The command is executed from the Nodeshell of each node cluster::> system node run -node <node_name> -command ifstat [ -z ] -a | <interface_name> cluster::> system node run -node node_example> -command ifstat e0a The -z argument clears the statistics The -a argument displays statistics for all network interfaces including the virtual host and the loopback address. Optionally, you can leave off the -a argument and specify the name of a network interface.
    • https://kb.netapp.com/on-prem/Switches/Brocade-KBs/Brocade_firmwarecommit_failed_error
      Applies to Brocade Switch Issue Firmware upgrade failed with error firmwarecommit failed
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Missing_SFP_information_on_used_Ethernet_ports_e0a_e0b_ports_are_down
      Applies to ONTAP 9 QSFP Issue e0b link down, no link lights, no SFP information slot 0: 10G/25G Ethernet Controller CX5 e0a MAC Address: d0:39:ea:1e:44:a8 (auto-25g_cr-fd-up) SFP Vendor: Molex SFP Par...Applies to ONTAP 9 QSFP Issue e0b link down, no link lights, no SFP information slot 0: 10G/25G Ethernet Controller CX5 e0a MAC Address: d0:39:ea:1e:44:a8 (auto-25g_cr-fd-up) SFP Vendor: Molex SFP Part Number: 1111455002 SFP Serial Number: 93A2012020609 e0b MAC Address: d0:39:ea:1e:44:a9 (auto-25g_cr-fd-up) SFP Vendor: SFP Part Number: SFP Serial Number: Device Type: CX5 PSID(NAP0000000006) Firmware Version: 16.25.1020
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/EMS_event_log_reports_Chassis_power_is_degraded_Power_Supply_Status_Critical
      ONTAP EMS event log reports, Chassis power is degraded, Power Supply Status Critical.
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/H410s_is_repeating_kernel_panic
      Applies to H410S-11110 H300S Issue The H410s node repeats the kernel panic even after entire node is replaced. Kernel panic(before node replacement): Kernel panic(after node replacement): The same sym...Applies to H410S-11110 H300S Issue The H410s node repeats the kernel panic even after entire node is replaced. Kernel panic(before node replacement): Kernel panic(after node replacement): The same symptom of those kernel panics: all those panics start from these error messages. bdx_uncore: probe of xxxx:xx:xx:x failed with error -22