Known issues
This section details the known issues in this version of IBM® Spectrum Connect and its solution components, along with possible solutions or workarounds (if available).
- HIPER – High Impact Pervasive. A critical issue that IBM has either fixed or plans to fix promptly. Requires immediate customer attention or code upgrade.
- High Impact – Potentially irrecoverable error that might impact data or access to data in rare cases or specific situations/configurations.
- Moderate – Limited functionality issue and/or performance issue with a noticeable effect.
- Service – Non-disruptive recoverable error that can be resolved through a workaround.
- Low – Low-impact usability-related issue.
- The issues listed below apply to Spectrum Connect 3.8.0 or earlier versions. As long as a newer version has not yet been released, a newer release notes edition for this release might be issued to provide a more updated list of known issues and workarounds.
- The following IBM Spectrum® Accelerate Family
storage systems are not supported in Spectrum Connect 3.8.0:
- IBM XIV® Storage System
- IBM Spectrum Accelerate
For the most recent information about known issues related to those storage systems, refer to the last edition of the release notes for Spectrum Connect 3.6.3.
- When a newer version is released for general availability, the 3.8.0 release notes will no longer be updated. Accordingly, check the release notes of the newer version to learn whether any newly discovered issues affect Spectrum Connect 3.8.0 or whether the newer version resolves any of the issues listed below.
| Ticket ID | Component | Severity | Description |
|---|---|---|---|
| SCB-6509 | IBM Spectrum Connect | High Impact | Mounting /tmp with noexec option
results in package installation failure. In the result of failure, the message License not
accepted is displayed instead of the license being displayed.To resolve this issue, mount /tmp with exec option, then remount it with noexec after successful installation of the Spectrum Connect software. |
| SCB-2222 | IBM Spectrum Connect | Moderate | Failure to resolve a DNS hostname may result in the rabbitmq
process malfunction. To avoid this issue, verify that the Spectrum Connect DNS hostname can be resolved. |
| SCB-5121 | IBM Spectrum Connect | Moderate | LDAP configuration is excluded from the backup and restore process. To resolve this issue, reconfigure the LDAP access after the Spectrum Connect is restored. |
| SCB-5915 | IBM Spectrum Connect | Moderate | A storage system that lost its connectivity to a Spectrum Connect instance,
cannot be removed from the web UI. Currently there is no solution or workaround for this limitation. |
| SCB-5927 | IBM Spectrum Connect | Moderate | User-defined credentials are not retained after the backup and restore
procedure. A restored Spectrum Connect installation reverts to the default username and password,
without informing the user. To resolve this issue, change the default user credentials after system restore. |
| SCB-6316 | IBM Spectrum Connect | Moderate | During upgrade from 3.4.x to any higher release, the initial setup wizard is
invoked automatically, even if all relevant configuration changes were made before the upgrade. To resolve this issue, log into Spectrum Connect CLI utility as ibmsc user and run the sc_setting modify -n CERTIFICATE_EXISTS -v TRUE command. |
| SCB-6594 | IBM Spectrum Connect | Moderate | When a new storage resource (child pool) is created within an unencrypted
parent pool on Spectrum Virtualize system, and attached to an encrypted service on Spectrum Connect,
the child pool might not be encrypted. Use the Spectrum Virtualize UI or CLI to verify encryption status of the pool. |
| SCB-6495 | IBM Spectrum Connect | Moderate | (Applies only to IBM Spectrum Virtualize Family storage systems.) When creating a paired resource, if the site name for a storage system has blank space, the creation fails. |
| SCB-6599 | IBM Spectrum Connect | Moderate | After unregistering Spectrum Connect from a VCenter (VC) as VASA Provider
(VP), the relevant VC entry is not removed from the database for up to 90 minutes. As a result,
service and resource changes are not allowed in the Spectrum Connect GUI for that
time. Workaround: Restart Spectrum Connect to clear the VC entry sooner. |
| SCB-7121 | IBM Spectrum Connect | Moderate | After clicking the Table View button to display the
existing storage resources as a table, the Domain column is not displayed as expected. Currently there is no solution or workaround for this limitation. |
| SCB-7127 | IBM Spectrum Connect | Moderate | It may be possible to attach a non-encrypted FlashSystem A9000 or A9000R
storage resource to an encryption enabled service. Currently there is no solution or workaround for this limitation. |
| SCB-85 | IBM Spectrum Connect | Service | Disconnected storage array disappear from the Spectrum Connect web interface after the
upgrade. To avoid this issue, before performing upgrade, verify that all storage arrays are connected to Spectrum Connect properly. |
| SCB-90 | IBM Spectrum Connect | Service | Spectrum Connect cannot use IPv6 addresses for management connection to
FlashSystem A9000 and A9000R storage systems. To resolve this issue, use IPv4 addressing, when configuring storage arrays. |
| SCB-165 | IBM Spectrum Connect | Service |
Editing the ldap.ini file manually may cause the Spectrum Connect LDAP integration failure. To avoid this issue, use the sc_ldap CLI command for LDAP configuration. |
| SCB-598 | IBM Spectrum Connect | Service | In some cases, the Celery service might hang when it is stopped. To resolve this issue, terminate the Celery background process by using the Linux® kill -9 command. |
| SCB-1023 | IBM Spectrum Connect | Service | Starting from 2.2.0, a vCO server must be added manually to the Spectrum
Connect. However, if the Spectrum Connect is upgraded from any previous release to 2.2.0 or later, a
vCO server is added automatically to the GUI. To resolve this issue, remove the vCO server manually after the upgrade is completed. |
| SCB-1355 | IBM Spectrum Connect | Service | LDAP configuration is reset after Spectrum Connect is upgraded from 2.1.1 to
2.2.0. Currently there is no solution or workaround for this limitation. |
| SCB-1359 | IBM Spectrum Connect | Service | If a software on IBM SAN Volume
Controller (SVC), which has been added to Spectrum Connect, is re-installed, the storage system
still appears connected, but does not function properly. To avoid this issue, remove SVC from Spectrum Connect after the SVC software is re-installed and connect the storage system to Spectrum Connect again. |
| SCB-1361 | IBM Spectrum Connect | Service | The user catalog on the storage systems that run Spectrum Virtualize is not updated
immediately after storage system credentials are changed via the Spectrum Connect GUI. Currently there is no solution or workaround for this limitation. |
| SCB-2517 | IBM Spectrum Connect | Service | The postgresql service does not start if the
/tmp folder does not have o+x access permission. To resolve this issue, configure the required permission for the/tmp folder, using the chmod o+x /tmp command. |
| SCB-2888 | IBM Spectrum Connect | Service | Installation fails when the root user has a default umask,
preventing other users from changing root-created directories. To avoid this issue, use the mkdir /opt/ibm and chmod 755 /opt/ibm commands to create the /opt/ibm folder and set correct permissions. |
| SCB-5126 | IBM Spectrum Connect | Service | After upgrading Spectrum Connect to 3.3.0, any LDAP user with the username
consisting of capital letters becomes a local user. To resolve this issue, change the local user to an LDAP user after upgrading Spectrum Connect to 3.3.0. |
| SCB-5837 | IBM Spectrum Connect | Service | The Spectrum Connect UI allows selection of the deduplication mode of data
reduction when defining a storage service for IBM FlashSystem® A9000 or A9000R storage systems. But, this mode is only supported for Spectrum
Virtualize storage systems. Currently there is no solution or workaround for this limitation. |
| SCB-377 | IBM Spectrum Connect | Low | If the IP address of a storage array changes, the
sc_storage_array CLI command is unable to update the IP address of the storage
array. In such a case, use the Spectrum Connect 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). |
| SCB-3660 | IBM Spectrum Connect | Low | On RHEL 7.x, due to the Django framework update, Spectrum Connect upgrade from
3.0.3 to 3.1.0 generates several warning messages about missing files. Despite the messages, the
upgrade completes correctly. Currently there is no solution or workaround for this limitation. |
| SCB-3845 | IBM Spectrum Connect | Low | Used capacity indication for storage services does not take into account the
space reserved for snapshots on FlashSystem A9000 and A9000R storage systems. As a result, the real
free hard capacity is less than displayed in Spectrum Connect. Currently there is no solution or workaround for this limitation. |
| SCB-4124 | IBM Spectrum Connect | Low | Storage resource (pool) capacity for the IBM FlashSystem A9000 and A9000R storage systems is limited to 1 PB. Any attempt
to create a storage resource exceeding 1 PB in size results in an error message. Currently there is no solution or workaround for this limitation. |
| SCB-4251 | IBM Spectrum Connect | Low | For Storwize® V7000 Unified storage
arrays, the microcode version number, build number, and system ID number are not consistent when
appearing in Spectrum Connect, vSphere Web Client, and storage system management GUIs. Different
version numbers and system IDs are displayed on each platform. Currently there is no solution or workaround for this limitation. |
| SCB-4252 | IBM Spectrum Connect | Low | The registration of Spectrum Connect as a VASA storage provider on the vCenter
server side might fail if an expired self-signed SSL certificate is present on Spectrum
Connect. To resolve this issue, replace the self-signed certificate as explained in the user guide. |
| SCB-4253 | IBM Spectrum Connect | Low | After an upgrade or reinstallation of Spectrum Connect, some DS8000® or SAN Volume Controller storage system identifiers might change,
causing Spectrum Connect to stop synchronizing with these storage systems. To resolve this issue, use the Spectrum Connect GUI or CLI to remove and then add back these storage systems. |
| SCB-5995 | IBM Spectrum Connect | Low | When Spectrum Virtualize action commands are based only on object names and
fail to find their object IDs in the audit log, Spectrum Connect cannot create their reference
configuration events. Currently there is no solution or workaround for this limitation. |
| SCB-7124 | IBM Spectrum Connect | Low | A storage LUN ID of more than 255 characters cannot be input for a FlashSystem
A9000 or A9000R volume added in vCenter, even though FlashSystem A9000R and A9000R support having a
LUN ID of more than 255 characters. Currently there is no solution or workaround for this limitation. |
| SCB-7160 | IBM Spectrum Connect | Low | PowerShell does not return correct or useful error messages for several
errors. Currently there is no solution or workaround for this limitation. |
| SCB-7161 | IBM Spectrum Connect | Low | After several Spectrum Connect connections are added in PowerShell, Spectrum
Connect users cannot log into the Spectrum Connect GUI, and errors are reported for the
attempts. Currently there is no solution or workaround for this limitation. |
| Ticket ID | Component | Severity | Description |
|---|---|---|---|
| SCB-1138 | IBM Storage Provider for VMware VASA | Moderate | A VM cannot be created on a datastore, if a size of thick-provisioned virtual
disk size is bigger than any of the Spectrum Virtualize child pools comprising the vDisk. To avoid this issue, make sure that at least one of the child pools has sufficient disk space to host the datastore vDisk. |
| SCB-1366 | IBM Storage Provider for VMware VASA | Moderate | Rescanning storage providers on VMware vCenter server results in rescan error,
if two Spectrum Connect instances are registered as storage providers for both VASA 1.0 and VASA 2.0
/ 3.0. To avoid this issue, register all Spectrum Connect instances as storage providers for either only VASA 1.0 or only VASA 2.0 / 3.0. |
| SCB-2518 | IBM Storage Provider for VMware VASA | Moderate | After a VM migration from a VVol-based datastore, the datastore may become
inaccessible via vWC. To resolve this issue, cancel registration of Spectrum Connect as a VASA storage provider, and run the registration again. |
| SCB-2531 | IBM Storage Provider for VMware VASA | Moderate | When migrating a VM into a VVol-based datastore, which does not support space
efficiency (thin or thick), the migration fails without a specific error message, explaining the
reason for the failure. To avoid this issue, create a VVol-enabled storage service that supports thick and thin provisioning. Then attach storage resources which will be able to support the correct destination VVol-based destination datastore. |
| SCB-2653 | IBM Storage Provider for VMware VASA | Moderate | Storage system information does not appear on the vCenter server after
registering Spectrum Connect as a storage provider for the first time. To resolve this issue, wait for several minutes after the initial registration attempt, and run the registration again. |
| SCB-3712 | IBM Storage Provider for VMware VASA | Moderate | Stretched capability of storage profile cannot be changed for virtual volumes on IBM SAN Volume Controller storage systems. Currently there is no solution or workaround for this limitation. |
| SCB-255 | IBM Storage Provider for VMware VASA | Service |
Cloning of a virtual machine from a VVol to another VVol on the same IBM SAN Volume Controller (SVC) fails, when the user chooses to customize the VM hardware during the cloning procedure. Moreover, resizing of the source and target VMs fails, if the SVC background copy is in progress. To avoid this issue, customize the virtual machine hardware only after the VM cloning and SVC background copy process are completed. |
| SCB-523 | IBM Storage Provider for VMware VASA | Service | If a storage system is removed and added to Spectrum Connect after its storage resource was
added to a VVol-enabled service, its previous configuration is not preserved after the addition.
This occurs if Spectrum Connect is not registered as a VASA provider. To avoid this issue, verify that Spectrum Connect is registered as a VASA provider before adding the storage system after its removal. In addition, after the storage system is added, it is recommended to check the vCenter log whether Spectrum Connect was identified as an active VASA provider. |
| SCB-1085 | IBM Storage Provider for VMware VASA | Service | When attempting to resize a virtual disk on a storage system, running Spectrum
Virtualize, while the disk formatting is in progress, vCenter displays the following error message:
'The disk extend operation failed:The VVol target encountered a vendor specific
error.'. To avoid this issue, resize the virtual disk only after the disk formatting process is finished. |
| SCB-2369 | IBM Storage Provider for VMware VASA | Service | A name of a VM, which is created on a VVol datastore, can have only
ASCII-based characters. Currently there is no solution or workaround for this limitation. |
| SCB-3351 | IBM Storage Provider for VMware VASA | Service | Resizing a VM based on an IBM SAN Volume
Controller stretched cluster can fail, if the two copies of the virtual volume are not
synchronized. To avoid this issue, wait for the synchronization to complete on storage system side. You can use the SVC lsvdisksyncprogress command to monitor synchronization progress. |
| SCB-3463 | IBM Storage Provider for VMware VASA | Service | The Edit Settings operation for a VVol-based VM fails, if a storage resource
used by the VM datastore has less free space than the VVol data disk of VM. To avoid this issue, make sure that the storage resource for the VM datastore has sufficient free space to accommodate the VVol data disk. |
| SCB-5586 | IBM Storage Provider for VMware VASA | Service | In deployments with more than one or two vCenter servers and two storage
providers with different priorities, a suspended and reactivated vCenter server fails to rescan the
providers. As a result, the storage providers remain inactive. To resolve this issue, disconnect the inactive storage providers and connect them again to the vCenter server(s). |
| Ticket ID | Component | Severity | Description |
|---|---|---|---|
| SCB-417 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | The tab of the IBM Storage Volume object shows incorrect mapping
information. Hosts that cannot access the datastore are shown as not being mapped to the LUN.
Currently there is no solution or workaround for this limitation. |
| SCB-447 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | When using the storage system management GUI (as opposed to the IBM Storage Enhancements GUI in vSphere Web Client) to map a
single volume to more than one ESXi hosts using different LUN IDs, the volume is not properly
recognized by vSphere Web Client and cannot be managed by the IBM Storage Enhancements. In addition, multiple errors might occur on the vSphere Web Client
during the use or modification of that volume. To avoid this issue, always use the same LUN ID when mapping a volume to multiple ESXi hosts via the storage system management GUI. |
| SCB-3654 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | When a vCenter user without storage management privileges adds a vCenter
interface to Spectrum Connect and then modifies the vCenter with the administrator credentials, logs
into vSphere Web client and performs volume operations, some of these operations may fail. To resolve this issue, remove the vCenter interface from Spectrum Connect, and add the vCenter again, using valid administrator credentials. |
| SCB-3759 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | After VMware vCenter reboot or upgrade, the changes made for the vCenter
before the reboot or upgrade fail to propagate to the IBM
extension for vCenter. To resolve this issue, restart the refresh vWC service by logging into the Spectrum Connect host as root and running the /etc/init.d/ibm_spectrum_connect restart_vwc_refresh command. |
| SCB-4184 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate |
Removing a vCenter interface from Spectrum Connect may cause unstable behavior of the vWC plug-in. To resolve this issue, perform one of the following procedures, depending on the Spectrum Connect
and vCenter deployment scenarios:
|
| SCB-4193 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | When provisioning a new volume using vSphere Web Client, the Max Provision
Size of the new volume is permanently set to 0. This results in volume creation failure. To avoid this issue, connect all vCenter servers in the SSO to the same Spectrum Connect instance. |
| SCB-5356 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | After upgrade to 3.4.0, in rare cases, Spectrum Connect might lose connection
with the vWC plug-in. To resolve this issue, restart the web plug-in service on the relevant vCenter server. |
| SCB-5841 | IBM Storage Enhancements for VMware vSphere Web Client | Moderate | A volume cannot be resized via vSphere Web Client. To resolve this issue, resize the volume using the storage system web-based user interface or CLI. |
| SCB-154 | IBM Storage Enhancements for VMware vSphere Web Client | Service | If a vCenter server is disconnected from Spectrum Connect during the upgrade,
the vWC extension appears with the previous version, when the vCenter server is re-activated. To resolve this issue, remove and reattach the vCenter server on Spectrum Connect. |
| SCB-399 | IBM Storage Enhancements for VMware vSphere Web Client | Service | If a volume is deleted, using vSphere Web Client, but the deletion fails on
the storage system, the volume is removed from the vSphere Web Client display. In this case, the
volume is successfully unmapped from the host, but there is no indication on the vSphere Web Client
that the volume still exists. To avoid this issue, delete the volume from the storage system directly. |
| SCB-671 | IBM Storage Enhancements for VMware vSphere Web Client | Service |
vWC volume creation and mapping task may fail if a source pool that exists on a FlashSystem A9000 or A9000R storage system within a domain has been attached to a service created by the default Spectrum Control user. To avoid this issue, associate the default Spectrum Connect user with the storage array domain. |
| SCB-701 | IBM Storage Enhancements for VMware vSphere Web Client | Service | A volume being moved between two FlashSystem A9000 or A9000R storage systems
using IBM Hyper-Scale Mobility cannot be unmapped in vWC from
the ESXi host after the source storage system enters the proxy mode. To resolve this issue, remove volume mapping using IBM Hyper-Scale Manager. |
| SCB-775 | IBM Storage Enhancements for VMware vSphere Web Client | Service | Creating a volume with minimum size (87 GB) on IBM FlashSystem A9000 or 9000R may fail, if the target pool size is smaller than 103 GB. To avoid this situation, increase the storage pool size to be 103 GB or bigger. |
| SCB-2479 | IBM Storage Enhancements for VMware vSphere Web Client | Service | Creating and mapping a volume on a FlashSystem A9000 or A9000R storage system
via the vWC plug-in may fail if a storage resource is connected to a host outside of a storage
system domain. To avoid this situation, verify that all the hosts defined on the vCenter are also defined on the storage systems and are associated with the domain. In addition, make sure that the default storage credentials defined in Spectrum Connect belong to the domain as well. |
| SCB-2519 | IBM Storage Enhancements for VMware vSphere Web Client | Service | Creating and mapping a volume on a FlashSystem A9000 or A9000R storage system
via the vWC plug-in may fail if ESXi LUNs used by the volumes do not belong to any domain, while the
Spectrum Connect storage credentials are associated with a specific domain. To avoid this situation, verify that volumes outside of a domain are not mapped to the target host. |
| SCB-3049 | IBM Storage Enhancements for VMware vSphere Web Client | Service | A connection session between Spectrum Connect and vCenter server remains open
after Spectrum Connect has been restarted or the vCenter server has been removed and added again via
the Spectrum Connect GUI. This results in multiple concurrent connection sessions with different IDs
between the servers. To resolve this issue, manually remove the redundant session via the vSphere Web Client (). |
| SCB-3063 | IBM Storage Enhancements for VMware vSphere Web Client | Service | When mapping a volume to several hosts that do not have a common storage
resource (pool), this operation may fail. To avoid this issue, verify that all hosts to be mapped share at least one storage resource on the same storage system. |
| SCB-3456 | IBM Storage Enhancements for VMware vSphere Web Client | Service | Resizing a stretched volume on IBM SAN
Volume Controller can fail, if the two copies of the volume are not synchronized. To avoid this issue, wait for the synchronization to complete on storage system side. You can use the SVC lsvdisksyncprogress command to monitor synchronization progress. |
| SCB-3637 | IBM Storage Enhancements for VMware vSphere Web Client | Service | If a volume is mapped to an ESXi 6.5 host, the size of the volume under the
IBM Storage Volumes tab does not change after its extension. To resolve this issue, rescan the host manually. |
| SCB-4525 | IBM Storage Enhancements for VMware vSphere Web Client | Service | Creation of several volumes and their subsequent renaming might fail in
mid-process with an error, indicating insufficient memory. As a result, some of the volumes are
created successfully, and some of them are not. Currently there is no solution or workaround for this limitation. |
| SCB-6287 | IBM Storage Enhancements for VMware vSphere Web Client | Service | There are inconsistencies in service capabilities as they appear in the
Spectrum Connect web UI and in the Flex-based version of the vWC plugin. For example, Data
Reduction: Deduplication in the Spectrum Connect UI is displayed as
Deduplication:Enabled, with spaceEfficiency:Thin in vWC.
Currently there is no solution or workaround for this limitation. |
| SCB-705 | IBM Storage Enhancements for VMware vSphere Web Client | Low | A volume, whose deletion fails, disappears from the volume list. The volume
reappears in the list after the next population. Currently there is no solution or workaround for this limitation. |
| SCB-836 | IBM Storage Enhancements for VMware vSphere Web Client | Low |
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. |
| SCB-838 | IBM Storage Enhancements for VMware vSphere Web Client | Low | If a volume is mapped to two or more ESXi hosts that are managed by more than
one vCenter server, volume operations fail. To avoid this issue, do not map a specific volume to ESXi hosts that are not managed by the same vCenter server. |
| SCB-2718 | IBM Storage Enhancements for VMware vSphere Web Client | Low | When delegating a single VVol-type service to several vCenter servers, the
service VVols will be exposed to all servers, even though they relate to only one of
them. Currently there is no solution or workaround for this limitation. |
| SCB-2970 | IBM Storage Enhancements for VMware vSphere Web Client | Low | Actions are allowed on volumes that are mapped to a disconnected or
non-responsive ESXi host. The volume actions will fail due to the host status. Moreover, if the
disconnected host is added to another vCenter server, the volume operations will fail on the new
server as well. To avoid this situation, verify that the host is connected to the vCenter server. If a disconnected or non-responsive host is connected to a new server, remove it from the original server to allow proper volume performance. |
| SCB-2974 | IBM Storage Enhancements for VMware vSphere Web Client | Low | When a LUN is shared between several ESXi hosts, its number must be the same
on all hosts. To avoid this situation, verify that the shared LUN number is available for all hosts. |
| SCB-2991 | IBM Storage Enhancements for VMware vSphere Web Client | Low | If a volume is shared between several datacenters, volume-related objects,
such as a datastore or a VM that belong to other datacenters, are missing from the vWC. Currently there is no solution or workaround for this limitation. |
| SCB-2999 | IBM Storage Enhancements for VMware vSphere Web Client | Low | When a disk is removed from a VM created on a VVol-based datastore, but not
removed from the datastore, the VM is still listed as a related object on the VVol. Currently there is no solution or workaround for this limitation. |
| SCB-6476 | IBM Storage Enhancements for VMware vSphere Web Client | Low | When a traditional (non-virtual) volume name is changed via Hyper-Scale
Manager or CLI management tool, the name does not change in vSphere UI. Currently there is no solution or workaround for this limitation. |
| Ticket ID | Component | Severity | Description |
|---|---|---|---|
| SCB-140 | IBM Storage Plug-in for VMware vRealize Orchestrator | Moderate | If the Map workflow uses initiators that are not
configured on the storage array, the workflow succeeds even though the initiators are silently
ignored. Currently there is no solution or workaround for this limitation. |
| Ticket ID | Component | Severity | Description |
|---|---|---|---|
| SCB-6562 | IBM Storage Management Pack for VMware vRealize Operations Manager | High Impact | LDAP authentication is not supported when connecting to vROps using Spectrum
Connect. To avoid this issue, use local accounts to access vROps. |
| SCB-796 | IBM Storage Management Pack for VMware vRealize Operations Manager | Moderate | When data collection interval is set to 1 minute, the array IOPS statistics
are presented as 0. Currently there is no solution or workaround for this limitation. |
| SCB-845 | IBM Storage Management Pack for VMware vRealize Operations Manager | Moderate | If the vROps server becomes unreachable while Spectrum Connect is still
reporting to it, the reporting ceases when the vROps server becomes reachable again. To resolve this issue, restart the Spectrum Connect service. |
| SCB-7062 | IBM Storage Management Pack for VMware vRealize Operations Manager | Moderate | After installing the new PAK file provided with Spectrum Connect 3.8.0 on the
vROps server, there will be two IBM Storage Management Pack
plugins, the old one and the new one. To resolve this issue, uninstall the old IBM Storage Management Pack plugin. |
| SCB-7165 | IBM Storage Management Pack for VMware vRealize Operations Manager | Moderate | When objects related to different arrays are given the same object name and
ID, they are merged into one object related to both arrays instead of existing as separate objects,
each related to its own array, as expected. Currently there is no solution or workaround for this limitation. |
| SCB-842 | IBM Storage Management Pack for VMware vRealize Operations Manager | Service | Duplicate thresholds might appear in vROps if a vROps server was removed from
Spectrum Connect and then re-added. To resolve this issue, delete the duplicate thresholds. |
| SCB-6171 | IBM Storage Management Pack for VMware vRealize Operations Manager | Service | Incorrect compliance information for Spectrum Virtualize objects is presented
in vROps 7.0. Currently there is no solution or workaround for this limitation. |
| SCB-844 | IBM Storage Management Pack for VMware vRealize Operations Manager | Low | If a storage object name contains spaces, it is displayed in the vROps custom
view with underlines instead of spaces. Currently there is no solution or workaround for this limitation. |