Release Notes— Fluid Cache for SAN for VMware Systems Release Notes — Fluid Cache for SAN 2.0.10 for VMware Systems Build Version: 2.0.
Release Notes— Fluid Cache for SAN for VMware Systems Contents PURPOSE OF THIS RELEASE................................................................................................................................. 3 FIXED ISSUES IN THIS RELEASE ............................................................................................................................ 3 SOFTWARE AND HARDWARE COMPATIBILITY ....................................................................................................
Release Notes— Fluid Cache for SAN for VMware Systems Purpose of this Release Fluid Cache for SAN for VMWare 2.0.10 is a maintenance release with the following focus: 1. Increase the robustness of automatically recovering from cluster node failures/reboots. 2. Fixed reported memory leaks within the VSA 3. Add support for 3-9 node clusters and 1 node non-expandable Note: Installation and Upgrade instructions for 2.0.10 are in the Dell Fluid Cache for SAN Version 2.0.
Release Notes— Fluid Cache for SAN for VMware Systems 2 nodes of 4 didn't shut down cleanly, came up with cachedev_failed and cachedev_failing CS assertion in empty_entry_cache_req_queue, ce_cache_req_lock already held CS assert in cs_assign_replica_data_eph() during cache restoration Network failure test CS assert(0 == (hp->cbh_flags & RNA_BSMD_HDR_FLAGS_RECOVERABLE)) failed at bsmd_cache_blocks.
Release Notes— Fluid Cache for SAN for VMware Systems unable to map cached volumes since doing a couple of VSA failures Extra claimrules attached to a LUN in the journal. claim rule files and path files in /tmp on the VSA are not being cleaned up incomplete error handling in add_claim.
Release Notes— Fluid Cache for SAN for VMware Systems kernel OOM due to fldc_cache at 95pct Initial resilvering doesn't complete for CS on restarted node Software and Hardware Compatibility Table 2 Hardware and Software Requirements Element Servers Dell PowerEdge systems that support Dell Express Flash PCIe SSDs and SRIOV: M620, M820, R620, R720, R820, R920, or T620 R730, R730XD, R630, or T630 Operating systems • ESXi 5.5 Update 2 (64-bit) Enterprise Plus ESXi 6.
Release Notes— Fluid Cache for SAN for VMware Systems Element Optional: Fluid Cache Client Servers (do not have SSDs but participate in a cluster) • All Dell PowerEdge systems (or non-Dell systems with a supported operating system that can install a supported Mellanox Ethernet adapter and support SR-IOV) Firmware and Driver Compatibility Table 3 Firmware and Driver Minimum Versions Element Minimum Version ESXi Mellanox ConnectX-3 Driver ESXi Mellanox ConnectX-3 Firmware 1.9.10.2 2.30.5118 Rack 2.30.
Release Notes— Fluid Cache for SAN for VMware Systems Known Issues Arising from Third Party Software The following issues are not caused by Fluid Cache itself, but arise from known issues in third party software. Cannot Enable Passthrough for NVMe Device in vSphere Web Client ISSUE: Using the vSphere web client, you cannot enable passthrough for Samsung NVMe SSD devices. WORKAROUND: Enable passthrough using the desktop version of vSphere. Known Issues in Fluid Cache for SAN 2.
Release Notes— Fluid Cache for SAN for VMware Systems Shutting Down Multiple Servers from an FLDC cluster ISSUE: Shutting down more than one server (host) from an FLDC cluster for maintenance purposes may cause potential performance issues and data loss. WORKAROUND: Dell recommends not shutting down multiple FLDC Cluster hosts at the same time to perform the updates.
Release Notes— Fluid Cache for SAN for VMware Systems return the user to the VMware console. The TUI may not exit immediately after entry of the padded number, but when the number is first used by the TUI to configure the VSA. WORKAROUND: Do not enter IP addresses with padded octets when using the TUI to configure the VSA. Issues with Samsung NVMe and Micron SSDs on Same Server ISSUE: Installing Samsung Electronics NVMe SSDs and Micron SSDs on the same server may cause heartbeat timeouts and other issues.
Release Notes— Fluid Cache for SAN for VMware Systems Then, add back any non-Fluid Cache claim rules, unmap all cached volumes (to clean out the journalled claim list rules), then remap the cached volumes. Cached Volume Mapping and Unmapping Failures Can Leave Stale Claim Rules ISSUE: In some circumstances the mapping and unmapping of cached volumes may fail leaving claim rules that hide known volumes on the ESXi host.
Release Notes— Fluid Cache for SAN for VMware Systems WORKAROUND: No action is required. The backing LUN will only appear temporarily and will be cleaned up within 24 hours. Guest VM I/O Timed Out or Experienced Very Long Delays ISSUE: Under some circumstances when the cache contains a large amount of dirty cache blocks, power cycling a node or removing a cache device in the cluster may cause I/O to hang in one or more of the guest VMs in the cluster.
Release Notes— Fluid Cache for SAN for VMware Systems f. The settings take effect immediately. You do not need to reboot the ESX/ESXi host. Not all Fluid Cache VSAs Started Correctly After a Cluster Shutdown or ESX Host Power Fail ISSUE: Under some circumstances VSAs are not started correctly following a cluster shutdown and restart, or an ESXi host power fail. This would appear in the EM console as a server that has not joined the cluster or cache devices are missing on a server.
Release Notes— Fluid Cache for SAN for VMware Systems Unable to add a Fluid Cache ESXi 6.0 host to an existing server cluster ISSUE: When configuring Fluid Cache VSA iSCSI interface on the Fuid Cache Cluster ESXi5.5U3 and ESXi6.0U1 platforms during VSA installation, the following error message is displayed. Cannot configure ISCSI initiator already configured for a different ESX host. WORKAROUND 1 (Preferred): Perform the following steps and configure the iSCSI section in the VSA setup. 1.
Release Notes— Fluid Cache for SAN for VMware Systems 1. 2. 3. 4. Perform the steps 1 through 5 as described in the deployment guide. Select Configure This Appliance and press . Configure your Backend Storage connection. Perform the steps 6 and 7 and continue with step 10 as provided in the deployment guide.
