Release Notes

Table 35. Known VMware Issues in Storage Manager 2019 R1 (continued)
Issue Description
Workaround: See VMware best practices documentation.
DSM-16665 After upgrading an ESXi host from version 5.5 to 6.0, Dell Storage Manager does not properly
reflect the host and its attributes as being ESXi 6 capable, in particular the recognition of the
protocol endpoint.
Workaround: Remove the server, and then add it back to Dell Storage Manager.
DSM-16656 If you select the Auto Manage Virtual Machines On Storage Centers option during the initial
Dell Storage Manager registration of a vCenter server, all the discovered ESXi hosts along with
their VMs are rendered within the Servers tree of the Storage panel. If any of these VMs are
later deleted from vCenter, they remain in the Dell Storage Manager view.
Workaround: To remove these deleted VMs from Dell Storage Manager, right-click the VM
and then delete it.
DSM-16248 On rare occasions, selecting Update information in the Dell Storage Manager Server view
results in the error java.net.SocketException: Unexpected end of file from
server.
Workaround: Despite the vCenter appearing to be online an able to accept connections, the
vCenter must be restarted to reestablish proper connectivity between Dell Storage Manager
and vCenter.
DSM-15879 The Host Setup wizard for VMware does not allow you to select an HBA on an ESXi host
that contains adapters that are not VMware software iSCSI adapters. When establishing an
integrated environment with Dell Storage Manager and VMware, various options are available
for you to import the VMware known inventory into Dell Storage Manager for enhanced
management benefits. You can choose to add hosts individually, or by creating and registering
from a vCenter server.
Workaround: Although the option exists in the Storage tab to create from vCenter server, the
preferred and more reliable method is to use the Dell Storage Manager Server tab. Select the
Server folder and then Register Server > Add VMware vCenter Server. Then, select Auto
Manage Storage Centers to populate the Storage Center.
DSM-15803 On rare occasions, when a vVol VM is migrated from one vVol datastore to another, a config
or data vVol might become orphaned on the original datastore. This vVol counts against the
total vVol scale, and takes up unnecessary space.
Workaround: Contact technical support to handle the removal of the VM.
DSM-15302 If you attempt to delete a datastore which is populated (not empty) using Dell Storage
Manager, an error results. A false indicator of connectivity is represented by a red X on the
vCenter server.
Workaround: Click the Update Information button in the top-level menu.
DSM-15000 A vVol VM snapshot with quiesce guest file-system option fails.
Workaround: Install the VMware Tools without the VSS feature. For more information, see
VMware Knowledge Base article number 2069952.
DSM-14997 When using sDRS with vVols, vCenter incorrectly recommends migrating the VM when both
vVols are on the same Storage Center.
Workaround: Review the recommendations from vCenter before taking action.
DSM-14891 A fast clone VM shows history with the VM from which it was created. Hence the data vVols
of this clone VM inherit the settings of the data vVols of the original VM. This shared history
also has the following consequences:
● Changing the Data Reduction profiles for a storage container might cause future fast
cloned VMs to be created with mismatched Data Reduction profiles for the config and data
vVols.
● If a user applies a VM Storage Policy to the original VM, the same changes apply to the
data vVols of the fast clone VM and conversely.
19