Release Notes

Dell - Internal Use - Confidential
Page 6 4/1/2016
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.
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.
WORKAROUND: This mixed configuration is not supported by Dell. Each server in the Fluid
Cache cluster may have Micron SSDs or Samsung NVMe SSDs, but not both.
VSA Agent Times Out and Exits When Connecting to vCenter
ISSUE: On some occasions, while attempting to connect to vCenter during startup, the VSA’s
agent service may timeout and then exit, causing the node to disconnect from the cluster. In
this event, the VSA is not fully functional, although it is shown as operational in vSphere.
Enterprise Manager shows the VSA as nonfunctional.
WORKAROUND: Restart the VSA.
Power-Cycling the ESXi Host Causes Claim Rules to Be Rewritten
ISSUE: In some circumstances, claim rules may be rewritten when power cycling an ESXi host.
WORKAROUND: Run the following commands on each ESXi host in the cluster to reset the
claim rule list to the default values:
~ # esxcli storage core claimrule remove --plugin=MASK_PATH
~ # esxcli storage core claimrule add --type=vendor --
vendor=DELL --model="Universal Xport" --plugin=MASK_PATH --
rule=101
~ # esxcli storage core claimrule load
~ # esxcli storage core claiming unclaim --type=plugin --
plugin=MASK_PATH
~ # esxcli storage core claimrule run