Version 3.0.1 (July 2016)

Version 3.0.1 replaced version 3.0.0. In addition, it introduced the following changes.

Ticket ID Description
SCB-2421 Enhancement: Memory utilization by IBM Storage Enhancements for VMware vSphere Web Client on the vCenter server has been vastly improved, resulting in better performance and resiliency.
SCB-2842 Enhancement: Performance of IBM Storage Enhancements for VMware vSphere Web Client has been optimized to improve the process of the vCenter object population. Now the application uses the VIM API to fetch only differences in configuration instead of populating the whole inventory.
SCB-488 Fixed: A volume cannot be moved to or from a child storage pool on IBM® Spectrum Virtualize (7.4), using vSphere Web Client.
SCB-527 Fixed: VASA 2.0 fails to connect to a storage array if only management port 1 is down and the rest of the management ports are available.
SCB-771 Fixed: The volumes listed in the Related Objects tab of vWC cannot be sorted by name.
SCB-839 Fixed: DS8000® volume creation might fail when mapping multiple volume groups to one ESXi host.
SCB-840 Fixed: Error message 'Could not connect to vSphere Web Client server' appears if the Spectrum Control Base software is upgraded without first logging out from vSphere Web Client.
SCB-1333 Fixed: When Spectrum Control Base is uninstalled and installed again, the storage services on its new instance that have the same name as the ones on the previous copy, are not recovered properly after failover to the standby instance. This occurs when the services are created before registering the Spectrum Control Base as VASA provider and results in the datastores becoming inaccessible.
SCB-2546 Fixed: When multiple vCenters use the same vWC server (same SSO domain), virtual volume instances may not properly appear in the vWC plug-in.
SCB-2554 Fixed: Advanced filtering tool for storage systems malfunctions in Mozilla Firefox browser.
SCB-2556 Fixed: When deploying the IBM Storage adapter on the vROps server, the PAK file version is displayed as version 1.0 instead of 3.0.0.