Version 3.0.0 (April 2016)
Version 3.0.0 introduced support for IBM FlashSystem® A9000 and IBM FlashSystem A9000R storage systems with microcode 12.0. In addition, this version introduced support for RHEL 7.0–7.2.
Version 3.0.0 included the following additional changes.
| Ticket ID | Description |
|---|---|
| SCB-1006 | Enhancement: The Spectrum Control Base web management interface introduces a new filtering mechanism for storage arrays and resources. The filtering is based on arbitrary text strings or storage system attributes. |
| SCB-1065 | Enhancement: The Spectrum Control Base web management
interface is enhanced and improved to support the abstracted storage provisioning method. Important: To ensure proper transition from the physical to abstracted storage provisioning,
additional configuration is required, as detailed in the Upgrading an existing installation
section of the Spectrum Control Base user guide.
|
| SCB-1773 | Enhancement: Deduplication option is added to the storage service capabilities for the FlashSystem A9000 and A9000R storage systems. |
| SCB-1919 | Enhancement: A guided configuration tour is invoked automatically after successful login to familiarize the user with the main elements of the Spectrum Control Base UI and principles of its operation. |
| SCB-1984 | Enhancement: To improve operation security, Spectrum Control Base requires manual opening of various TCP ports prior to package installation. |
| SCB-2049 | Enhancement: The scb_port_change.sh script is added for changing the TCP port used by Spectrum Control Base. |
| SCB-109 | Change: IBM Storage Plug-in for VMware vRealize Orchestrator is deployed, using a configuration workflow. |
| SCB-929 | Change: The IBM Storage Plug-in for VMware vRealize Orchestrator uses abstracted storage entities (spaces and services) instead of physical objects (pools and storage systems). |
| SCB-1045 | Change: As a result of introduction of abstracted storage provisioning, instead of providing physical capabilities for the LUNs visible in ESXi , a storage service name is exposed via VASA. This is the service that the volume resides on. |
| SCB-1051 | Change: During a VM storage policy creation, a VVol-enabled storage service is exposed in the vWC plug-in as a capability value of the IBM Storage Service entry. The storage space is presented as a VVol container. This information is displayed in the storage_container:storage_service format. |
| SCB-1406 | Change: Spectrum Control Base generates messages to inform the user when volume capabilities are compatible or not with storage service requirements. The volume compatibility alarms are propagated to vCenter server via VASA API as well. |
| SCB-1912 | Change: The storage resource name, over-provisioning and snapshot reserve parameters are introduced in the Add New Resource dialog box. |
| SCB-2062 | Change: VVol-enabled services become available in the vWC plug-in. This presents relations of a VVol to its VM and storage service. |
| SCB-2463 | Change: As a result of introduction of abstracted storage provisioning, the LUN parameter in the vWC plug-in Create New Volume dialog box is changed to Suggested LUN. |
| SCB-190 | Fixed: Changes of the DS8000 storage system connectivity or its user access level are not propagated to the vWC plug-in. |
| SCB-794 | Fixed: The ibm_spectrum_control and the rsyslog services do not load properly after the Spectrum Control Base reboot. |
| SCB-1264 | Fixed: The Spectrum Control Base GUI does not limit the storage service name length. As a result, a storage resource creation may fail, if a length of its automatically assigned name exceeds 64 characters. The storage resource name consist of the following elements: service name_pool_identification suffix. |
| SCB-1607 | Fixed: When creating and mapping of a volume to a host is in progress, an attempt to create another volume and map it to the same host may fail. This occurs because the second volume will use the same LUN ID as the first one. |