5.4.0 Limitations and Known Issues for IBM Spectrum Control

General IBM Spectrum Control issues

The License parameter on the About the Installation page of the IBM Spectrum Control 5.4.0 GUI does not display the correct value when only the IBM Spectrum Control Select Edition license is applied.

If only the IBM Spectrum Control Select Edition license is applied on your IBM Spectrum Control 5.4.0 system, the License parameter on the About the Installation page displays an incorrect value of Storage Capacity Units and Select. The correct value is Select.

_{____________________}

APAR IT31680: Showing zero value for some IBM SAN Volume Controller and IBM Storwize storage capacities

IBM Spectrum Control and IBM Storage Insights are showing zero values for some storage capacities values such as Physical Capacity and Allocated Capacity for monitored SAN Volume Controller or Storwize storage systems that run firmware level below 8.2.

IBM Spectrum Control and IBM Storage Insights are showing zero values for some storage capacities values such as Physical Capacity and Allocated Capacity for monitored SAN Volume Controller or Storwize storage systems that run firmware level below 8.2.

_{____________________}

APAR IT31680: Showing zero value for some IBM SAN Volume Controller and IBM Storwize storage capacities

IBM Spectrum Control and IBM Storage Insights are showing zero values for some storage capacities values such as Physical Capacity and Allocated Capacity for monitored SAN Volume Controller or Storwize storage systems that run firmware level below 8.2.

This issue happens due to an SAN Volume Controller CLI 8.1.x limitation surfacing which is visible in IBM Spectrum Control and IBM Storage Insights after upgrading to 5.3.5 or higher, where the capacity values for SAN Volume Controller family devices had changed to rely on the SAN Volume Controller physical capacity values.

The issue only affects SAN Volume Controller family devices, and does not impact FlashSystem 900 devices.

The issue is resolved in the newer versions of SAN Volume Controller firmware, starting with:

• 8.1.3.6
• 8.2.1.4

For details see SAN Volume Controller APAR HU01916: The GUI Dashboard and the CLI lssystem command report physical capacity incorrectly
https://public.dhe.ibm.com/storage/san/sanvc/release_notes/813_releasenotes.html#APARs

_{____________________}

APAR IT24763: Adding or modifying the connection information for an IBM FlashSystem V9000 or FlashSystem V840

When you add or modify the connection information for FlashSystem V9000 or FlashSystem V840, you must provide the credentials of a user that can connect to the control nodes of these storage systems.

If you provide the credentials of a user that can connect to the internal FlashSystem 900 or FlashSystem 840 module rather than the control nodes, the probe will fail.

The probe error that is generated is "CMMVC7205E The command failed because it is not supported".

IBM Spectrum Control can manage the control nodes of a FlashSystem V9000 or a FlashSystem V840 cluster, but it can't manage the back-end FlashSystem module.

_{____________________}

APAR IT23975: Port down/offline alerts generated for FlashSystem 900 when the port is simply unused/disconnected.

IBM Spectrum Control is generating "error" alerts for an IBM FlashSystem 900 storage device for ports that are not physically connected to a SAN.  IBM Spectrum Control is receiving port alerts for ports that are known to be disconnected, and no matter the suppression settings selected, the alerts continue to be generated. 

This differs from the way that all other IBM storage operates, including SAN Volume Controller, Storwize, and other IBM storage where unused ports do not trigger alerts and do not report errors about unused ports.  Typically, port alerts should only trigger if a port that was connected then becomes disconnected.  That is how the rest of IBM storage environment operates.  At this time, there is no way to make this behavior consistent with other IBM storage.

The alert for an inactive and configured FlashSystem port is working as designed because the condition is an "offline" status, which aligns with the FlashSystem GUI.  Inactive and unconfigured FlashSystem ports do not represent an error condition to generate alerts in IBM Spectrum Control.  The different port status inactive configured / inactive unconfigured reported by FlashSystem device are due to the installed small form-factor pluggable (SFP) transceivers onto the interface card in the system canister.  When SFP is installed and the port is not connected, the status reported by FlashSystem is inactive and configured port.

The workaround for changing the port status is to remove the unused SFP and reset the interface card in the canister.  More information how to add/remove SFPs to the FlashSystem storage enclosure can be found in the FlashSystem knowledge center at https://www.ibm.com/support/knowledgecenter/STKMQB_1.6.1/com.ibm.storage.flashsystem900.1.6.1.doc/tms_add_sfps.html.

_{____________________}

Incorrect overhead capacity value for block storage systems

IBM Spectrum Control might report an incorrect overhead capacity for some block storage systems such as XIV, EMC Unity, FlashSystem 9100 and FlashSystem A9000.

_{____________________}

HDS back-end storage devices behind a SAN Volume  shows as "not monitored"

IBM support worked with Hitachi support and this is the answer from Hitachi:  We have identified the root cause and are working on new SVP SMI-S Provider code to fix the issue.

Details: When IBM SMI-S Spectrum Control version 5.2.15.0 sends query “HITACHI_StorageProcessorSystem”, the Controller ID on DKC1 side that the SVP SMI-S provider calculates was incorrect; so IBM SMI-S Spectrum Control version 5.2.15.0 does not receive the port information for DKC1 side correctly from the SVP.
 
Unfortunately there is no workaround at present. The permanent fix will be to upgrade to the new code. You can see the status of this APAR here: http://www.ibm.com/support/docview.wss?uid=swg1IT25032

_{____________________}

In Metro Mirror or Global Copy relationship, if a Peer to Peer Remote Copy (PPRC) is terminated and then deleted on one of the storage systems, the other storage system retains the relationship  
If a storage system is not aware of the termination due to the loss of the PPRC path, volumes on that system might be counted as both unprotected and protected.

To correct the reporting, take one of the following actions:

• Issue a terminate to the storage system, which retains the relationships.
• Reestablish the PPRC paths and the relationship by using the dscli command or another copy services management tool (such as the CSM product).

Enabled ethernet port that is not connected to a switch can cause the GUI to hang  

On some IBM servers running Windows 2012, an enabled ethernet port can cause the IBM Spectrum Control GUI to stop responding if the port is not connected to a switch.  This condition causes a Db2 SQL -911 error and also causes the IBM Spectrum Control GUI to stop responding.

To prevent this, disable the ethernet port or configure the port by using the instructions at  https://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp?topic=/com.ibm.bladecenter.hs22.doc/dw1iu_t_lan_over_usb_install_windows_driver_install.html

_{____________________}

Disable Windows User Account Control to edit configuration files

On Windows installations, if you installed IBM Spectrum Control by using a domain user account, you must disable User Account Control to edit the IBM Spectrum Control configuration files.

_{____________________}

Spectrum Scale cluster with configured sudo-wrapper environment can not be managed with Spectrum Control or Storage Insights

This configuration is not supported since mmdsh commands are needed to collect various configuration information from the Scale Cluster.  

_{____________________}

IBM Spectrum Control cannot detect the mount status of file systems on Storwize V7000 Unified storage systems   

If a file system is manually unmounted from a Storwize® V7000 Unified storage system, IBM Spectrum Control cannot detect that the file system was unmounted. Because of this limitation, information that is displayed in the IBM Spectrum Control GUIs is not accurate and some storage-related actions on the file system might fail.

For example, when you provision storage, a file system on a Storwize V7000 Unified storage system might be recommended for provisioning. However, if that file system was manually unmounted after it was first detected by IBM Spectrum Control, the provisioning action will fail. An unmounted file system cannot be used for provisioning. To avoid this issue, ensure that the monitored file systems on the Storwize V7000 Unified storage system are mounted before you run the provisioning action.

_{____________________}

IBM SAN Volume Controller and IBM Storwize devices might not accurately report used space of data reduction pools and deduplicated volumes

When an SAN Volume Controller or Storwize device is configured with data reduction pools, it (on certain firmware levels, including 8.1.3.3) no longer reports the used space for a specific volume, and the tier distribution is no longer reported.  This is a limitation from the firmware with data reduction pools/deduplicated volumes.

Setting the rate at which data is copied between volumes that run IBM Spectrum Virtualize

IBM Spectrum Control can do tasks that significantly alter the structure of storage. For example, IBM Spectrum Control can add a mirrored volume copy, or migrate volumes from one pool to another by using storage optimization functions. When IBM Spectrum Control performs these tasks, a default synchronization rate of 100% is set.

For more information about how to change the synchronization rate, see the "Changing the synchronization rate for volumes on SAN Volume Controller or Storwize family systems"  https://www.ibm.com/support/knowledgecenter/SS5R93_5.4.0/com.ibm.spectrum.sc.doc/tbs_svc_setting_sync_rate.html.

_{____________________}

Probes with a Storage Resource agent (SRA) on Linux servers hang and remain "In Progress" forever

SRA probes run Logical Volume Manager (LVM) commands and these can hang which causes the SRA to hang and appear to be "In Progress" indefinitely.  

To verify that this is the situation causing the hang, view the SRA agent trace log on the SRA Deployment and verify that the last command was an LVM one.

To recover from this situation:

1. Kill the hung SRA process
2. Kill the hung LVM command
3. From a command line, retry the LVM command and verify that it runs successfully. If it does not, use the LVM documentation to repair the LVM so that it does.  
4. Restart the SRA

You can follow the progress of the APAR related to this issue here:  http://www.ibm.com/support/docview.wss?uid=swg1IT15105

_{____________________}

RHEL known issues with fprintd-pam module (fingerprint authentication module)

• https://access.redhat.com/solutions/44386
• https://bugzilla.redhat.com/show_bug.cgi?id=1010844

_{____________________}

Application Groups and Aggregated Metrics 

For application groups, the performance data is aggregated from the volumes added to the group, either directly or using a filter.  The values displayed for the aggregated Read Response Time, Write Response Time, and Overall Response Time are incorrect.  All other metrics currently supported for application aggregation are rendered correctly.

_{____________________}

IBM Spectrum Control might report incorrect vmdk size and incorrect capacity of VM

IBM Spectrum Control persists the relation between a vmdk and vmdisk, restricting the relation to vmdisk <-> current vmdk file. The current vmdk file has an aggregate size which includes the sizes of snapshots up to the current vmdk file. IBM Spectrum Control associates the latest running delta file with vmdisk, hence IBM Spectrum Control might report the size smaller than actual size of the vmdisk if there are newer snapshots (which are not included in the current vmdk size).

_{____________________}

Export Performance Data Tool  

The output format from the exportPerformanceData Script was changed, starting in IBM Spectrum Control 5.3.7.  To minimize the impact of this and all future output format changes,  users of the CSV files are encouraged to parse the column headers they are interested in.

Non-IBM Storage Support Issues

Non-IBM storage devices will only show node relationships in the Volumes table if the relationship is 1:1.  Therefore if a volume resides on more than 1 node, the node column will be empty for that volume.

EMC Support Issues

In 5.3.0 and later, you can view more information about the capacity, space usage, and performance of EMC™ storage systems. However, keep in mind the following issues for EMC support:

On the details page for an EMC storage system, duplicate NAS nodes might be displayed if the EMC's NAS Servers support both NFS and CIFS protocols. This issue occurs because each protocol represents a node. For example, on the same NAS server, if NAS1451 supports NFS and NAS1451 supports CIFS protocols, two node entries are displayed on the details page for the storage system.

Information about both FC and Serial Attached SCSI (SAS) ports are returned when FC ports are probed.

VNXe:
Thin-provisioned volumes: The value for allocated space is incorrect.
Total or available capacity values of each storage tier in a storage pool are incorrect.

VNX:
Thin pools: The value for physical allocated space is incorrect.
File system pools are not displayed.
Total or available capacity values of each storage tier in a storage pool are incorrect.
The VNX regular thin pool's "pool capacity" value, returned by EMC SMI-S provider, is slightly lower than reported by the element manager.  This applies only to VNX thin pool, referred to as "Pools" in Unisphere.
Disk and volume response times and utilization percentages: The displayed values for these metrics are higher than their actual value.
 
VMAX3:
Available pool space or any allocated capacity values are always 0.
All aggregated volume capacity values are 0 because of the missing relationship between pools and volumes.
Mappings of volume to pool and volume to disk are not displayed.

Reporting: In Cognos Analytics, pre-defined reports might not be available for EMC storage systems.

Unity:
In 5.3.5 and later, you can monitor Unity devices. Due to the mismatch of old FS UID format from 5.3.5 probe and new FS UID format from 5.3.6 and later PM data collection, no file system metrics will be displayed until a manual or next schedule probe  / data collection is run on Unity.
 

NetApp Support Issues

For NetApp systems Copy Data can not correlate data, so no links are shown.
 

HDS Support Issues

Viewing managed disks 

Hitachi VSP systems are supported as virtualizers and show the backend storage system and external disks.  It is not possible to show managed disks mapped directly to a host.

Problems monitoring performance on Hitachi VSP storage systems  

Pure Support Issues

If IBM Spectrum Control is monitoring a Pure system that is in asynchronous relationship with another storage system, details of the target system are not available.  IBM Spectrum Control will list the target system however the remote volumes can not be correlated hence a link will not be displayed in the user interface. 

If IBM Spectrum Control is monitoring only the target system of asynchronous relationships, no details of the source system are available.
 

Cognos Analytics

_{____________________}

Cognos Analytics 11.1.4, bundled with Spectrum Control, does not support Db2 11.5  

If you plan to use IBM® Cognos® Business Intelligence reports in IBM Spectrum Control, you can install IBM® Cognos® Analytics 11.0.9 or later (up to and including 11.1.4) and migrate your reports. 

Currently, Cognos Analytics does not support Db2 11.5, so if you plan on using Cognos Analytics we strongly suggest using Db2 11.1.x for Spectrum Control to avoid problems with Cognos Analytics report integration.  To continue to use Cognos Analytics, use Db2 11.1 parts listed here:  https://www.ibm.com/support/pages/node/6205756.  Review supported platforms matrix to ensure all products you plan to install on the machine support the same level of Db2: https://www.ibm.com/support/pages/ibm-spectrum-control-53x-servers-agents-and-browsers.

_{____________________}

GPFS/GSS/Spectrum Scale is not supported in Cognos Analytics

GPFS/GSS/Spectrum Scale™ file systems are not correctly represented in Cognos reports and are not supported in Cognos.

Information is not collected about NFS and CIFS exports that are defined on a GPFS/GSS/Spectrum Scale clusters.

_{____________________}

Spectrum Scale is not supported in Cognos Analytics

GPFS/GSS/Spectrum Scale™ file systems are not correctly represented in Cognos reports and are not supported in Cognos.

_{____________________}

Links to Help in IBM Spectrum Control 5.4.0 predefined reports open the public IBM Spectrum Control Knowledge Center

When using the Cognos Analytics User Interface to generate IBM Spectrum Control predefined reports, the Help link will open the IBM Spectrum Control Knowledge Center on ibm.com.  The system running Cognos Analytics will need access to the internet to open to the knowledge center.  

 

Documentation Updates and Corrections

Incorrect information about the minimum version of Fabric OS for Brocade switches

Information about the minimum version of Fabric OS that is required to connect directly to Brocade switches is incorrect in the non-English documentation for IBM Spectrum Control 5.4.0. In some places, the documentation states that Fabric OS 8.2 or later is required. The correct minimum version is Fabric OS 8.2.1.

The following non-English documents are affected:

• IBM Spectrum Control 5.4.0 Administrator's Guide
• IBM Spectrum Control 5.4.0 Installation Guide
• IBM Spectrum Control 5.4.0 Knowledge Center