Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 7 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ESX_Hosts_losing_access_to_LUNs_regularly_along_with_Aggregate_reporting_long_CP_s
      Applies to VMware critical alert for datastore path down Poor performance and alerts for SQL virtual machines Affected datastores: Path redundancy to storage device naa.xyz degraded. Path vmhba1:C0:T7...Applies to VMware critical alert for datastore path down Poor performance and alerts for SQL virtual machines Affected datastores: Path redundancy to storage device naa.xyz degraded. Path vmhba1:C0:T78:L10 is down. ONTAP reports long or back2back consistency points (CP) wafl_exempt00: wafl.cp.toolong:error]: Aggregate_xyz_sata_aggr1 experienced a long CP. I/O latency increased from average value of 8000 microseconds to 1000008 microseconds
    • https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/VMware_Atomic_Test_and_Set_heartbeats_impact_connectivity_to_storage
      2022-04-04T12:33:16.355Z cpu1:2097617)NMP: nmp_ThrottleLogForDevice:3872: Cmd 0x89 (0x45bac31031c0, 2097193) to dev "naa.600a09803831364468244e4c5a47494e" on path "vmhba64:C1:T0:L0" Failed: H:0x5 D:0x...2022-04-04T12:33:16.355Z cpu1:2097617)NMP: nmp_ThrottleLogForDevice:3872: Cmd 0x89 (0x45bac31031c0, 2097193) to dev "naa.600a09803831364468244e4c5a47494e" on path "vmhba64:C1:T0:L0" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. 2022-04-04T12:43:13.402Z cpu2:2097617)NMP: nmp_ThrottleLogForDevice:3872: Cmd 0x89 (0x45baf1751140, 2097193) to dev "naa.600a09803831364468244e4c5a47494e" on path "vmhba64:C0:T0:L0" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
    • https://kb.netapp.com/on-prem/Switches/Brocade-KBs/Brocade_Defect_DEFECT000568423___I_O_abort_issue_on_the_host
      Applies to FCoE FCIP Fabric Operating System (FOS) v7.2.1 Switch 7800/FX8024 Brocade Issue Frequent I/O abort issues on the ESX host.
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/ESXi_hosts_may_lose_connection_to_LUNs_after_MetroCluster_switchover_switchback_due_to_bug_CSCve72490
      When doing an MCC switchover or switchback, ESXi hosts may lose connection to (boot) LUNs, and need to be rebooted to recover access. The LIF extended status post Switchover was seen as "FDISC error -...When doing an MCC switchover or switchback, ESXi hosts may lose connection to (boot) LUNs, and need to be rebooted to recover access. The LIF extended status post Switchover was seen as "FDISC error - ID could not be acquired for this virtual port". Event:E_DEBUG, length:177, at 289527 usecs after Tue Jun 19 15:56:40 2018[825307441] ns_reg_port_name(261): OTH: Trying to register duplicate port name for port-id 0xb20162 Existing entry's detail: pWWN , fWWN
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NAS_workload_performs_poorly_compared_to_local_disk_or_SAN
      Applies to Any Hypervisor or SAN client Any version of Data ONTAP Issue When copying a folder with multiple small files, a local drive copies in less time than copying to or from a NAS share or betwee...Applies to Any Hypervisor or SAN client Any version of Data ONTAP Issue When copying a folder with multiple small files, a local drive copies in less time than copying to or from a NAS share or between two different NAS shares After migrating a server from a physical host to a VM, overall performance of the VM is poor in comparison from a disk latency perspective Performance may be up to 10x slower on a CIFS share or NFS export compared to a comparable SAN LUN or local set of disks copying files
    • https://kb.netapp.com/Legacy/NetApp_HCI/OS/Compute_node_boots_directly_to_Ember_instead_ESXi
      Applies to NetApp HCI compute nodes Issue Compute node boots directly to NetApp Configurator (EmberOS) instead of the ESXi
    • https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/Cluster_refresh_operation_on_the_ONTAP_Select_failing_after_deploy_upgrade
      Applies to ONTAP Select Issue Node storage pool information refresh failed for node "cluster02-01". Reason: None."