Release Notes
Issue Description
DSM-13274 The Dell Storage Manager VASA Provider, whether using VASA1 or VASA2, can have only one
vCenter server registered to it at any time. You cannot register multiple vCenter servers to the
Dell VASA Provider at the same time. If you register a vCenter server to Dell Storage Manager
and then register the server to the Dell VASA Provider, you rst must unregister the server from
the VASA Provider before registering a dierent vCenter server to the Dell VASA Provider.
Workaround: If you try to register any vCenter server to the Dell VASA Provider, and the
registration fails, make sure that no other vCenter servers are registered to the Dell VASA
Provider.
DSM-13042 Under rare circumstances, usually involving VVol operations (cloning and snapshots) on multiple
VMs concurrently using scripting and eventual deletion of VVols, an attempt to delete a VVol VM
might result in VVols not being deleted. This scenario results in inecient space consumption and
reduction in total VVols available for future use.
Workaround: Removal of the VVols is not a user-level corrective option. Contact Dell Technical
Support for assistance. Avoid running concurrent VVol operations using scripting. Instead, script
sequential operations or operations with interjected delays.
DSM-12732 It is possible to create a storage container, and a subsequent VVol datastore using it, of a logical
size that exceeds the physical capacity of the storage array. The capacity values (in the vCenter
user interface) for an oversubscribing container reect the actual free or total physical capacity
values of the array instead of the logical storage container values.
Workaround: None.
DSM-12728 In rare occurrences, the space consumption information for a volume might be blank.
Workaround: Close and reopen your client.
DSM-11945 Even after unregistering VASA, powered-o VMs are accessible and VVol datastores are active. If
you try to power on the VMs or create a new VM, vCenter eventually discovers that the VASA
Provider is not present and it marks the VVol datastores as inactive.
Workaround: None.
DSM-11417 When high availability (HA) is congured between two hosts, VVols are migrated from the active
host to the standby host when management network access to the active host is lost. This
situation is similar to VMFS, and is the expected behavior. However, if only the data network goes
down, VMFS datastores migrate to the standby host, but VVols do not fail over. VMCP currently
is not supported with VVols.
Workaround: No workarounds are available when the data network goes down, but the
management network stays up. However, if the management network to the active host goes
down, failover is triggered, regardless of the state of the data network .
DSM-9825 If you create a storage container in Dell Storage Manager, and then create a datastore from
vCenter, there could be a delay before the VASA Provider detects the datastore.
Workaround: Dell recommends that you create VVol datastores from Dell Storage Manager. This
task creates the storage container on the Storage Center and the datastore on vCenter in one
operation. If you want to create the storage container in Dell Storage Manager, and then create
the datastore from vCenter, you will need to wait 1-2 minutes after creating the storage container
in
Dell Storage Manager before it is visible in vCenter. After the new storage container is visible in
vCenter, the VVol datastore can be created.
DSM-151 vCenter displays the VVol datastore as active even after a storage container is deleted from Dell
Storage Manager. If you try to create a VM on the datastore, it is marked as inactive.
Workaround: None.
22