Applies to ONTAP Select HD1 – 9.91GB - VMDK that represents the cf card (or boot device) HD2 – 120GB - VMDK for the CORE file (this space is reserved to store corefiles generated after a Kernel or use...Applies to ONTAP Select HD1 – 9.91GB - VMDK that represents the cf card (or boot device) HD2 – 120GB - VMDK for the CORE file (this space is reserved to store corefiles generated after a Kernel or userspace panics) HD3 – 4GB - VMDK for the NVRAM (virtualized NVRAM or vNVRAM) Do NOT change properties of the VMDKs (example: thick to thin provisioning) as this is not supported and may result in Cluster malfunction and possible re-deployment. For any queries please contact NetApp Support.
Applies to ONTAP Select VMware Issue Node reboots. The following panic string is seen in logs: k.panic: Panic String: vnvram_flush: sim_kern_nvram_write_n failed with 5 in process vnvram_flush_thread ...Applies to ONTAP Select VMware Issue Node reboots. The following panic string is seen in logs: k.panic: Panic String: vnvram_flush: sim_kern_nvram_write_n failed with 5 in process vnvram_flush_thread on release 9.6P2 (C) In VMware ESXi VMkernel logs, following messages are seen: HB at offset 3178496 - Waiting for timed out HB esx.problem.vmfs.heartbeat.timedout vob.vmfs.heartbeat.timedout
