Dell PowerVault MD3000i Dell MD Storage Array vCenter Plug-in User’s - Page 44

Restrictions The following issues have been identified within this release and the following workarounds must be used to resolve them. Table 1-1. Restrictions ID P200098715 P200085031 P200097562 P200088431 P200085831 Description Workaround Changing the password of a If the storage array password is storage array does not changed, remove and re-add the prevent the Plug-In from storage array to the Plug-In or edit displaying the storage array the settings of the storage array properties. Any changes to from the Plug-In and set the the storage array from the password field to the current plug-in will fail, however. password. The Plug-In does not reflect the name change after performing a clear configuration on the storage array. If the storage array configuration is cleared from PowerVault Modular Disk Storage Manager, the storage array must be removed and re-added to the Plug-In to detect the change. Default host group Explicitly map a virtual disk to the mappings are not displayed ESX host or host group to prevent within vCenter Plug-In. If the default host group virtual no virtual disks are mapped disks from being mapped. to the ESX host or host group, mappings from the default host group are used and not displayed within the vCenter Plug-In. The installation log does not contain any information about the Pegasus service starting. After installation, verify that the cimserver service has been started from services.msc window. The Plug-In displays Due to the limited return codes improper error messages in from SMI-S provider, some error some situations. codes might be erroneous. Include all information and details when troubleshooting these errors. 44 Dell MD Storage Array vCenter Plug-in