Release Notes
Open Issues Related to VVols
The following open issues are related to virtual volumes (VVols).
Issue Description
DSM-30674 After restarting the Data Collector service, VVols storage containers might be inactive.
Workaround: Unregister the VASA provider then register the VASA provider again.
DSM-27446 Storage Manager does not display information for VVols or VMFS volumes in the Connectivity tab
in the Servers view.
Workaround: View VVols or VMFS information from the Storage view.
DSM-16665 After upgrading an ESXi host from version 5.5 to 6.0, Dell Storage Manager does not properly
reect the host and its attributes as being ESXi 6 capable, in particular the recognition of the
protocol endpoint. An extra artifact is that a VVol datastore is identied with improper size of 0B.
Workaround: Remove the server and then add it back to Dell Storage Manager.
DSM-16659 If a VVol VM's disk is resized, and you perform Update information, the storage container's
congured space does not reect the modied value.
Workaround: Exit and restart the Dell Storage Manager. The Dell Storage Manager client shows
the changes to the disk size.
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 still 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 occurrences, 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, a restart
of vCenter is needed to reestablish proper connectivity between Dell Storage Manager and
vCenter. A case for this has been logged with VMware.
DSM-15980 By design, a storage container on the Storage Center created by one Dell Storage Manager Data
Collector cannot be managed by another Dell Storage Manager. However, you can select the
storage container, and attempt to create a datastore.Dell Storage Manager should lter out
storage containers it does not manage from the list of available storage containers.
Workaround: Select a storage container which was created by the same Dell Storage Manager.
Alternatively, use vCenter to create the datastore from an existing storage container. vCenter
properly lters the available storage containers.
DSM-15879 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 benets. 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 then Register Server → Add VMware vCenter Server. Then, select Auto Manage
Storage Centers to populate the Storage Center.
DSM-15803 In rare circumstances when migrating a VVol VM from one VVol datastore to another, a cong or
data VVol might become orphaned on the original datastore. This VVol counts against the total
VVol scale, and takes up unnecessary space.
20