Version 3.1.0 (December 2016)
Version 3.1.0 introduced support for new releases of the VMware platforms (vCenter, vWC, vRO, vROps). The additional changes were as follows.
| Ticket ID | Description |
|---|---|
| SCB-879 | Enhancement: Added the availability capability for a storage service, enabling the use of stretched clusters on IBM SAN Volume Controller systems. |
| SCB-934 | Enhancement: Added the Quality of Service (QoS) capability for the Spectrum Accelerate Family storage services, enabling the use of volumes or storage resources according to predefined service levels. |
| SCB-2940 | Enhancement: Improved handling of VMware virtual volumes (VVols), allowing for multiple VVol-enabled services to reside on a single storage space. Also, a new resource attachment method is used to attach several storage resources from different storage systems to one service. |
| SCB-2650 | Change: Upgraded Django Python Web framework to version 1.8. |
| SCB-3038 | Change: Introduced new methods of server authentication and token storage, using the current VMware SDK tools. |
| SCB-898 | Fixed: IBM Spectrum Virtualize Family products do not support updating storage profile for virtual volumes. |
| SCB-2634 | Fixed: When the TCP port 5672 is opened for the rabbitmq process, it accepts all traffic, compromising connection security. |
| SCB-2750 | Fixed: When creating a new volume on a DS8000 storage system immediately deleting another one, the new volume state might appear as "Pending deletion". |
| SCB-2878 | Fixed: If an IBM SAN Volume Controller is removed from the target list on an ESXi host, the storage system retains its connectivity and allows operations on itself. |
| SCB-3046 | Fixed: A cloned virtual volume is displayed as a snapshot VVol. |
| SCB-3146 | Fixed: When hot cloning a VM with a snapshot from a VVol-based datastore on a host to another datastore on a different host, may cause the operating system on the destination datastore to fail. |
| SCB-3184 | Fixed: Spectrum Control Base UI allows attaching multiple storage resources from the same storage system to a VVol-based service, although only a single pool attachment is currently supported. |
| SCB-3187 | Fixed: On IBM SAN Volume Controller (SVC) with microcode prior to version 7.8, if a snapshot is made for a VM cloned from a VVol-based VM or a template, restoring from this snapshot and then performing hot migration of the VM during I/Os, may result in data loss. |
| SCB-3209 | Fixed: Changing VVol-related configuration on Spectrum Control Base after the storage system, holding the VVol metadata information, was detached from Spectrum Control Base, and then connected again, can cause malfunction in IBM Storage Provider for VMware VASA. |
| SCB-3232 | Fixed: Cloning a VVol-based VM may result in the VM operating system
failure, when the following conditions exist:
|
| SCB-3509 | Fixed: Adding a storage system with a back-resolving IP address to Spectrum Control Base fails, if the resulting DNS name has no address association. |