Release Notes— Fluid Cache for SAN for VMware Systems Release Notes — Fluid Cache for SAN 2.1.0 for VMware Systems Build Version: 2.1.
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.1.0 is a maintenance release with the following focus: Improve diagnostic capability when there are cluster issues Improve cluster shutdown robustness Fix stability issues and improve cluster operation Support rolling upgrades from 2.0.10 Note: Installation and Upgrade instructions for 2.1.0 are in the Dell Fluid Cache for SAN Version 2.1.
Release Notes— Fluid Cache for SAN for VMware Systems Operational improvement Issues with shutting down VSA Issues with write phase of compare and write Shutdown failure scenario MD Crash due to unresolved duplicates Performance degradation during unaligned I/Os Cache device could not be used I/O timeouts and errors after cache network failure Data loss in multiple failure scenario Mellanox updated driver (fixes a PSOD) Software and Hardware Compatibility See Dell Fluid Cache for SAN Co
Release Notes— Fluid Cache for SAN for VMware Systems WORKAROUND: WORKAROUND: Contact Dell Customer Support for assistance in resolving this issue. Removing a Server from a Cluster ISSUE: If you try to remove a server from a cluster before shutting down the server, Enterprise Manager displays a message that the action is not allowed.
Release Notes— Fluid Cache for SAN for VMware Systems ISSUE: When configuring the VSA using the Text-based User Interface (TUI), entering a padded address (e.g., 172.19.2.018) causes the TUI to abruptly exit without a visible error message and 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.
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 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. WORKAROUND: Using vSphere, reboot the VSA on the server that is reporting issues.
