Release Notes

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.
WORKAROUND: Using vSphere, reboot the VSA on the server that is reporting issues.
Unmapping Multiple Cached Volumes Can Leave Cluster in a Degraded
State
ISSUE: In some circumstances, during the unmapping of multiple cached volumes fluid cache
servers can be left in a degraded state. This would appear in the EM console as a server that
has left the cluster or a server that is missing cache devices.
WORKAROUND: Using vSphere, reboot the VSA on the server that is reporting issues.
Unable to add a Fluid Cache ESXi 6.0 host to an existing server cluster
ISSUE: Using Enterprise Manager GUI, if you try to add an ESXi 6.0 Fluid Cache host to an
existing server cluster within a Storage Center, the following error message is displayed:
SC servers must all have the same operating system.
WORKAROUND: When adding a new Fluid Cache ESXi6.0 server host to an existing sub server
cluster, in the Edit Server Settings dialog box, select VMware ESXi 5.5 for the Operating System
type instead of VMware ESXi 6.0. After adding the server to the sub server cluster, when
Enterprise Manager prompts you to change the version, change the operating system type to
VMware ESXi 6.0.
This method enables you to add an ESXi 6.0 host to an existing sub server cluster on the SC8000
without any issue.
Dell - Internal Use - Confidential
Page 13 3/9/2015