Release Notes

Dell - Internal Use - Confidential
Page 7 4/1/2016
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.
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
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.
Backing LUN of cached volume appears in vCenter
ISSUE: When performing a multiple (bulk) cache mapping of LUNs, there is the possibility that
the backing (uncached) LUN will temporarily appear in vCenter. Important: this LUN should not
be used or accessed. It is for internal Fluid Cache usage only.
A backing LUN can be identified by an 8 in the 8th octet from the right of its identifier. See the
example below:
36000d31000eea10000000000800000aa – Backing LUN that may temporarily appear in vCenter
– DO NOT USE
36000d31000eea10000000000000000aa – identifier that would appear in Enterprise Manager
and is the real cached LUN.