SCW Disk Provisioning Resolution Guide
Applies to
- SnapCenter Server (SC)
- SnapCenter Plug-In for Windows (SCW)
Description
Common errors when attempting to provision disks with SnapCenter Plug-In for Windows
Cause | Solution |
No storage connection is set for StorageSystem | Configure name resolution for SVM management |
Connection on port 443 for protocol HTTPS timed out | Test network connection and increase SVM timeout |
No SAN connectivity between host and storage controller | Enable ISCSI session or FCP path |
The client and server cannot communicate, because they do not possess a common algorithm | Enable SchUseStrongCrypto=1 for .NET |
Failed to format volume [Error Code:5] | Enable disk automount |
Shared disk fails to create windows file system | Move Available Storage to cluster owner node |
Shared disk fails while retrieving physical disk resource information | Configure iGroup with initiators from all MSFC nodes |
Failed to get disk information | Verify WMI is healthy |
SCW assigns the incorrect mountpoint | Enable SetDiskOnlineWhileDiskProvisioning=True |
RDM can be provisioned only on guest operating systems based on ESX | Install or update VMware tools |
Vserver API missing Vserver parameter | Add SVMs to SnapCenter |
Additional Information
additionalInformation_text