Known issues

Volumes that were migrated from an XIV® storage array (A) to another XIV storage array (B) using Hyper-Scale Mobility (online volume migration) might not be manageable.

This specifically occurs if the volumes on the original XIV storage array (A) are deleted from the storage array (A), and then the same volume IDs are reused on that storage array (A).

If both XIV systems (A and B) are connected to the same Spectrum Control and this situation occurs, it prevents the management of these volumes through Spectrum Control.

Currently there is no solution or workaround for this limitation.

Currently there is no solution or workaround for this limitation.

To resolve this issue, replace the self-signed certificate as explained in the user guide.

This is to prevent repeated login attempt failures after which the directory server blocks that user account.

In such a case, update the storage admin credentials on the storage array with which the login has failed. Alternatively, you can remove that specific storage array from Spectrum Control and then reset the credentials.

You can find the relevant storage array by checking the events.log log file. For example:

Mar 26 13:50:01 ronend-sc1  ERROR ID:SC-0008 |
Severity:ERROR | Parameters:reason=Logging in to
array 2810-214-MN65025 has failed with the provided
credentials.
,user_name=ronenu | Message:Storage credentials for 
user ronenu were disabled. Reason: Logging in to
array 2810-214-MN65025 has failed with the provided
credentials.

To resolve this issue, use the Spectrum Control GUI or CLI to remove and then add back these storage arrays.

To resolve this issue, disable the Internet Explorer Enhanced Security Configuration option.

In such a case, use the Spectrum Control GUI to edit and update the IP address of the storage array (In the Arrays pane, move the mouse pointer over an array that you want to update, and then click the Edit button).

To resolve this issue, terminate the Celery background process by using the Linux kill -9 command.

This occurs if the LUN number is already associated with a volume outside of the XIV domain.

Currently there is no solution or workaround for this limitation.

As a result, volumes that were mapped to an empty cluster must be manually unmapped.

To avoid this issue: before mapping volumes to an XIV array, delete all empty cluster configurations on that array, or add at least one host to each empty cluster.

Stopping Django service ... [OK]
Stopping Celery services ... [OK]
Stopping DS8K proxy.....[FAILED]

To resolve this issue, terminate all the Java background processes and then restart the Spectrum Control service.

Currently there is no solution or workaround for this limitation.

Currently there is no solution or workaround for this limitation.

Currently there is no solution or workaround for this limitation.

To resolve this issue, remove and reattach the vCenter server on Spectrum Control.

To avoid this issue, set the Spectrum Control server clock to the correct time before the installation.

To resolve this issue, delete all hosts defined without domain, and add these hosts again with valid domain settings.

To resolve this issue, use IPv4 addressing, when configuring storage arrays.

To avoid this issue, before performing upgrade, verify that all storage arrays are connected to Spectrum Control properly.

Currently there is no solution or workaround for this limitation.

In such a case, determine whether the IBM Tivoli Storage Productivity Center capabilities are sufficient for replacing the IBM Storage Provider for VMware VASA. If the IBM Storage Provider for VMware VASA is still needed, IBM TPC 5.2 (or later) provides a method of excluding storage arrays from a specific storage provider, allowing you to remove the array association with the IBM TPC provider.

For more information, refer to the IBM Tivoli Storage Productivity Center documentation.

To avoid this issue, do not include spaces in the IP interface name of the XIV storage array.

To resolve this issue, delete the space and the service from the standby Spectrum Control manually.

To avoid this issue, verify that Spectrum Control is registered as a VASA provider before adding the array after its removal. In addition, after the array is added, it is recommended to check the vCenter log whether Spectrum Control was identified as an active VASA provider.

To resolve this issue, unregister Spectrum Control as a storage provider on the vCenter server.

To avoid this issue, verify that both service and storage array have matching capabilities before the attachment.

If a combination of both iSCSI and FC initiator port types is defined for an ESXi host, mapping volumes to that ESXi host causes both iSCSI and FC to be used for those volumes.

To avoid this situation, use the storage system management tools to define only one active protocol type (iSCSI or FC) for the initiators of each ESXi host.

To avoid this issue, always use the same LUN ID when mapping a volume to multiple ESXi hosts via the storage system management GUI.

Currently there is no solution or workaround for this limitation.

Currently there is no solution or workaround for this limitation.

To avoid this issue, do not map a specific volume to ESXi hosts that are not managed by the same vCenter server.

To avoid this error on the Spectrum Control side, log out of vSphere Web Client before upgrading the Spectrum Control software.

To avoid this issue, keep the default value of 300 or keep the value higher than 1.

To avoid this issue, unmap the volume before deleting it.

If you encounter this problem, configure only one volume group for one ESXi host when creating and mapping a volume.

To avoid this issue, manually add port 9443 to the URL, when launching vSphere Web Client. Use the following format https://<host>:9443/vsphere-client.

Currently there is no solution or workaround for this limitation.

To resolve this issue, log into vCenter Managed Object Browser (MOB) at https://<vCenter_server_IP>/mob., using your vCenter credentials.

Navigate to Content > ExtensionManager > UnregisterExtension.

Enter com.ibm.storage.vwc, when a pop-up window is displayed, and click Invoke Method twice.

Repeat registration of the vCenter server on the newly connected Spectrum Control.

Currently there is no solution or workaround for this limitation.

Currently there is no solution or workaround for this limitation.

Currently there is no solution or workaround for this limitation.

To resolve this issue, manually update to the thresholds in vCOps to match the XIV microcode that you are using.

Currently there is no solution or workaround for this limitation.

To resolve this issue, delete the duplicate thresholds.

To resolve this issue, restart the Spectrum Control service.