Known Issues

DataCore SANsymphony 10.0 PSP18

VMFS Tier Fix

Instances have been observed in which each storage device is assigned the same individual tier (computed based on the maximum tier - If the maximum tier chosen is 6, each storage device will be assigned 3 as the tier) rather than the ones assigned by Expert Pool configuration step, when the selected data source mode is Virtual Machine File System (VMFS). As a workaround, set individual tiers to each storage device after the deployment.

IPv6 Configuration

DataCore Installation Manager for vSphere is using IPv4 only, but the operating system starts with IPv6 name resolution first if available. Make sure to configure the correct corresponding setting or disable IPv6.

DataCore SANsymphony 10.0 PSP16 Update 1

Different Credentials: Deployment fails due to differences in the credentials. As a result, it is recommended to use the same credentials on both the deployed virtual machines and the machine where the DataCore Installation Manager for vSphere is running. Also, if the selected language packs are French (fr-FR) and Spanish (en-ES), the default administrator accounts in the deployed virtual machines will be "Administrateur" and "Administrador" respectively. Consequently, the machine where the DataCore Installation Manager for vSphere is running will require the same default administrator account (i.e.  "Administrateur" or "Administrador").

DataCore SANsymphony 10.0 PSP 12 Update 2

Language Pack: The addition of nodes with different language packs is not supported.

DataCore SANsymphony 10.0 PSP 12 Update 1

Unattended Deployment

The DataCore Installation Manager for vSphere unattended deployment requires the user to input if the vCenter has more than one Datacenter. There are two options to workaround. Either choose a datacenter during the unattended deployment and the deployment will continue or, to run the deployment with only one Datacenter in the vCenter.

DataCore SANsymphony 10.0 PSP 11

vCenter Plugin

The Installation of vCenter Plugin fails because a former installed vCenter Plugin was not removed correctly or is already registered. There is no warning on the DIMv GUI.The vSphere Plugin is not accessible through vCenter as expected and a "page not found" error is displayed.

Workaround:

  1. Copy the vCenter Plugin package to the SDS-VM
  2. Install vCenter Plugin manually and re-register if asked
  3. Logout on the vCenter and login again afterward

Storage Array Type Plug-Ins

The ESXi fails to add Storage Array Type Plug-Ins (SATP) rules, when the SATP rules already exist.

Workaround:

Enter the SATP rule manually using the below command from CLI:

ESXicli storage nmp satp rule add -V DataCore -M "Virtual Disk" -s VMW_SATP_ALUA -c tpgs_on -P VMW_PSP_RR -O "iops=10 disable_action_OnRetryErrors"

DataCore SANsymphony 10.0 PSP 10

Default Password

The password generated by DataCore Installation Manager for vSphere is hidden after you load the XML deployment plan using the Load button. If you proceed with the deployment, you will not be able to log into the virtual machines. To avoid this issue, click Edit and enter a password before you click Deploy.

DataCore SANsymphony 10.0 PSP 7

CPU Reservation

In some rare cases, the CPU reservation of a virtual machine may be set to 75% instead of 100% due to insufficient capacity per physical CPU. For details on adjusting CPU reservation, see https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/latency-sensitive-perf-vsphere55-white-paper.pdf

Also refer to DataCore FAQ 1277 (Known Issues: Third Party Hardware and Software).