5.2 Limitations and known issues for Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication

Content

This document is a list of the limitations and known issues for Tivoli Storage Productivity Center Version 5.2 and Tivoli Storage Productivity Center for Replication Version 5.2.

To access all of the support documentation, including alerts, APARs, or known issues for previous releases, go to the IBM Support Portal.

For information about the devices that are supported by Tivoli Storage Productivity Center Version 5.2, see the support matrix at https://www.ibm.com/support/docview.wss?uid=swg21386446.

To see the IBM Tivoli Storage Productivity Center Version 5.2 Quick Installation Guide, see the Printable Documentation page in the Tivoli Storage Productivity Center knowledge center.

APAR IT11343: Tivoli Storage Productivity Center for System z documentation incorrectly references the portdef.props configuration file

The Tivoli Storage Productivity Center for System z Installation Guide, User's Guide, and Knowledge Center contain references to the "portdef.props" configuration file. These publications should reference the "bootstrap.properties" file in the
path_prefix/opt/Tivoli/RM/wlp/usr/servers/replicationServer/ location. This incorrect reference to portdef.props occurs in two topics in the System z documentation:
Ports
Starting the Tivoli Storage Productivity Center for Replication for System z GUI

You can track the status of this APAR here: https://www-01.ibm.com/support/entdocview.wss?uid=swg1IT11343

The documentation incorrectly states that single sign-on can be configured for DS8000 Storage Manager, SAN Volume Controller, and Storwize V7000

In the product documentation, there are instructions for how to configure single sign-on between Tivoli Storage Productivity Center and DS8000 Storage Manager, SAN Volume Controller, and Storwize V7000. However, the single sign-on function is not enabled for this release. It is recommended that you ignore the documentation related to single sign-on for external applications.

The Tivoli Storage Productivity Center Select Edition Version 5.2 license name is incorrect in the Product licenses information center topic

In the Product licenses information center topic in the English version of the IBM Tivoli Storage Productivity Center Version 5.2 User's Guide, the license name for the Select Edition should be IBM Tivoli Storage Productivity Center Select Edition. This issue also exists in the translated Tivoli Storage Productivity Center Version 5.2 information center and the IBM Tivoli Storage Productivity Center Version 5.2 Installation Guide.

Ignore references to Configuration Utility and Tivoli Integrated Portal in the product documentation

The Tivoli Storage Productivity Center Knowledge Center incorrectly references the Configuration Utility and Tivoli Integrated Portal as components of Tivoli Storage Productivity Center. These components are no longer included with Tivoli Storage Productivity Center and references to these components can be ignored.

Installing Jazz for Service Management

The following information applies to the installation of Jazz for Service Management:

• To install Jazz for Service Management and Tivoli Common Reporting, the following compressed files must be downloaded and extracted to a single directory (for example, c:\downloads\JazzSM):
• Jazz for Service Management
• Tivoli Common Reporting
• Tivoli Common Reporting
• IBM WebSphere Application Server

• Disk space requirements for each server on which you plan to install Jazz for Service Management and Tivoli Common Reporting. If you are using downloaded installation packages from Passport Advantage Online or IBM Fix Central, the downloaded packages must be unpacked to a local disk or file system on each server on which you install these two components.
• Windows:
• 5 GB free disk space on the C: drive for temporary installation files and other necessary files that will remain on the server
• 10 GB additional free disk space on the target installation disk for the Jazz for Service Management and Tivoli Common Reporting program files
• Additional free disk space for the installation images, including the images that you download and the resulting unpacked files; this might require as much as 10 GB additional free disk space
• AIX/Linux:
• 5 GB free disk space on the root file system for temporary installation files and other necessary files that will remain on the serve
• 10 GB additional free disk space on the target installation disk for the Jazz for Service Management and Tivoli Common Reporting program files]
• Additional free disk space for the installation images, including the images that you download and the resulting unpacked files; this might require as much as 10 GB additional free disk space

Manually creating the Windows service for the Jazz™ for Service Management Version 1.1.0.1 server

On Windows operating systems, one of the consequences of not starting the Jazz for Service Management Version 1.1.0.1 installation program from the Tivoli Storage Productivity Version 5.2 installation program is that the Windows Service for the Jazz for Service Management Version 1.1.0.1 server is not created.

To manually create a Windows Service for the Jazz for Service Management Version 1.1.0.1 server, complete the following steps:

1. At the command prompt, go to the JazzSM_install_directory\bin directory.
2. Run the following command:

smsetApplicationServer.bat --property autostart=true --property admin.name=JazzSM_username --property admin.password=JazzSM_password

where JazzSM_username is the user name that is used to log on to the Jazz for Service Management WebSphere profile, and JazzSM_password is the password for the Jazz for Service Management user name.

This issue will be fixed in a future release of Jazz for Service Management.

Documentation update: Port numbers must be manually validated when installing Jazz for Service Management without a web browser

The topic Installing Jazz for Service Management and Tivoli Common Reporting on AIX without a web browser is missing information about manually validating port numbers during the installation of Jazz for Service Management. Step 19 in this procedure should be:


19. Review your port configuration and click Next.

Important: You must verify that the ports you specify on this page are
available and not being used by other applications. If any of the specified
ports are in use, change those values to ports you know are available before
installing Jazz for Service Management.

Attention: If you are upgrading from Tivoli Storage Productivity Center
Version 4.2.2 to Version 5.2 (or later), Jazz for Service Management and IBM
Tivoli Integrated Portal can use port 16310. If there is a port conflict, you must
change the value of the HTTP transport port.

This update applies to the topic in the 5.2 Knowledge Center and the 5.2 Installation Guide.


Windows environment variables can cause errors when installing or upgrading the Device server

On Windows operating systems, before you install Tivoli Storage Productivity Center Version 5.2 or upgrade to Version 5.2, ensure that the following environment variables do not exist:

• JAVA
• DEVICESERVER
• WS-LAUNCH.JAR

If you do not remove these variables, an error occurs when you install or upgrade the Device server.

Displaying the web-based GUI in high contrast mode

You might encounter minor issues if you view the web-based GUI in high contrast mode. For example, if you enter invalid data in a field, an error message is displayed but the field is not highlighted.

Tivoli Storage Productivity Center information center topics are missing information

The following Tivoli Storage Productivity Center information center topics are missing a note that describes the conditions under which single-sign on is supported:

• Planning for LDAP
• Configuring Tivoli Storage Productivity Center and Jazz for Service Management for single sign-on

For the complete text, see the doc_corrections PDF attachment.

PDF files do not export correctly in languages and locations with non-Latin 1 code pages

In the Tivoli Storage Productivity Center web-based and stand-alone GUIs, PDF files do not export correctly in languages and locations where non-Latin 1 code pages are used. When you try to export the file, the non-Latin 1 characters are stripped from the output.

The affected languages are:

• Chinese (Simplified)
• Chinese (Traditional)
• Czech
• Hungarian
• Japanese
• Korean
• Polish
• Russian

When you export to CSV and HTML, the correct output is generated in all languages and locations.

You must use Tivoli Common Reporting to generate reports and export these reports as PDF files. For more information about exporting reports as PDF files, see IBM Cognos Business Intelligence information center Version 10.1.1. Search for Export Data in PDF Format.

Installing DB2 using a Windows domain user account requires Schema Administration authority

If you are installing DB2 using a Windows domain user account, you must first log on to Windows using a domain administrator user account that has Schema Administration authority. Otherwise the DB2 installation task will fail. The requirement for Schema Administration authority was omitted from the Knowledge Center topic describing this installation process: "Installing DB2 by using a Windows domain user account".

Cluster data for a Storwize device is not available in Tivoli Storage Productivity Center after a Tier 3 or 4 recovery procedure

After a Tier 3 or 4 recovery procedure is performed on a system that was previously probed by Tivoli Storage Productivity Center, the cluster data for some systems is no longer available in the Tivoli Storage Productivity Center web-based GUI.

This issue occurs with the following systems:

• SAN Volume Controller
• Storwize V7000 Unified
• Storwize V7000
• Storwize V3700
• Storwize V3500

To resolve this issue, remove the affected storage system from Tivoli Storage Productivity Center and then add the storage system again. To gather data on the storage system, run a discovery job and probe job.

The installation of Tivoli Common Reporting fails with insufficient space on the disk partition

The Tivoli Common Reporting installation program fails when the DB2 Content Store database for Tivoli Common Reporting is installed on a different server from the server on which you plan to install Jazz for Service Management and Tivoli Common Reporting. The Tivoli Common Reporting installation program fails when 8 KB of additional DB2 table space is requested from the disk partition because there is not enough space on the disk partition.

To resolve this issue, ensure that you have sufficient space in the remote disk partition for the DB2 table space before you install Tivoli Common Reporting.

This issue will be fixed in a future release of Tivoli Common Reporting.

Incorrect roles-to-group mappings in Tivoli Storage Productivity Center Version 5.1 (or later) result in login issues after you upgrade to Tivoli Storage Productivity Center Version 5.2

In Tivoli Storage Productivity Center Version 5.1 (or later), if you did not complete a correct roles-to-group mapping, you can experience login issues in the web-based GUI after you upgrade to Version 5.2. These issues occur because there was no roles-to-group mapping validation in previous Tivoli Storage Productivity Center versions.

Tip: Role-to-group mapping is defined as one group that is mapped to one role and this group is declared at the operating system level.

To avoid this issue, after you upgrade to Tivoli Storage Productivity Center Version 5.2, log in to the web-based GUI by using one of the following credentials:

• A valid root ID (on UNIX operating systems)
• A valid administrator ID (on Windows operating systems)

The Administrator role in Version 5.2 was the superuser role in Version 5.1.

To correct the previous role-to-group mapping, after you log in to the web-based GUI, click Setting > User management.

The navigation tree for the help is not visible

When you first access online help from the web-based GUI, the navigation tree for the help might not be visible. To make it visible, refresh the browser window that contains the help.

The provisioning task is deleted if you return to the Provision Storage wizard

When you complete the steps in the Provision Storage wizard, Tivoli Storage Productivity Center determines the best location for the storage and displays a provisioning task. Depending on your role and permissions, you can save, run, or schedule the provisioning task. However, if you return to the Provision Storage wizard, the provisioning task is deleted. You can resubmit the provisioning request, but Tivoli Storage Productivity Center recalculates the storage placement recommendation. The storage placement recommendation is recalculated even if you do not modify any of the requested storage specifications.

Error messages for failed data collection jobs might be unclear

Some error messages in the logs for data collection jobs do not specify clearly why the task failed. For example, you might see that a request failed "due to rc (number)" notification.

If this error occurs, run the job again.

The source location for DB2 Version 10.1 or later is not required for DB2 Version 9.7

The Jazz for Service Management installation wizard includes the field The IBM DB2 10.1 or later, Enterprise Server Edition installation image on the Specify Source Locations page of the wizard. If you leave this field blank, the following message is displayed:

The IBM DB2 10.1 or later, Enterprise Server Edition installation image field is empty.
This field is required when you want to install DB2.

If you are using DB2 Version 9.7, disregard this message and leave the field blank.

For a list of DB2 versions and fix packs that you can use with Tivoli Storage Productivity Center Version 5.2, see the support matrix at https://www.ibm.com/support/docview.wss?uid=swg21386446. Click the 5.2.x link under Agents, Servers and Browsers.

Return code of -10012 is generated when you run wizards

If a return code of -10012 is generated when you run the Analyze Tiering, Balance Pools, or Transform Storage wizards, it means that the analysis of the storage virtualizer resources completed with a warning. To determine the cause of the warning, read the warning message in the log file for the task.

Cannot report detailed back-end storage information for a DS5000 or a DS4000 system

If a SAN Volume Controller uses back-end storage from a DS5000 system or a DS4000 system, some information about the back-end storage might be missing. If you did not create explicit host connections for the back-end disks on the DS5000 or DS4000 system, the following problems might occur:

• The CIM agent for the DS5000 or DS4000 system does not report any detailed information about the back-end storage.
• Tivoli Storage Productivity Center cannot provide other information about the back-end storage for the consuming disk system. For example, Tivoli Storage Productivity Center cannot provide RAID information.

Therefore, you must create explicit host connections for the back-end disks on the DS5000 or DS4000 system. It is not sufficient to associate the back-end disks with the default host group.

Informational message HWNLM0557I is generated if the maximum I/O capability is not available

If insufficient performance data was collected when you ran the Transform Storage wizard, the maximum I/O capability of the target pools is analyzed to generate recommendations. If the information that is required to calculate the maximum I/O capability is not available, then default values are used and the informational message HWNLM0557I is generated. To add the information, go to the Pools page, right-click the pool, and then click View Properties. On the Back-End Storage tab, click Edit.

Tivoli Storage Productivity Center cannot detect the mount status of file systems on Scale Out Network Attached Storage and Storwize V7000 Unified storage systems

If a file system is manually unmounted from an IBM® Scale Out Network Attached Storage (SONAS) or Storwize V7000 Unified storage system, Tivoli Storage Productivity Center cannot detect that the file system was unmounted. Because of this limitation, information that is displayed in the Tivoli Storage Productivity Center 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 Tivoli Storage Productivity Center, 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.

No storage pools displayed in the results of a balance analysis task

If no recommendations are made when you run a balance analysis task, the storage pools that are analyzed are not displayed in the results.

Using a virtual private network connection to install Tivoli Storage Productivity Center can cause problems

Do not use a virtual private network (VPN) connection to install Tivoli Storage Productivity Center. This type of network connection can create problems with the installation.

If you are using a VPN connection, disconnect it before you install Tivoli Storage Productivity Center. After you install Tivoli Storage Productivity Center, you can reconnect the VPN connection.

The Brocade Network Advisor SMI-S agent cannot provide the list of ports for a fibre channel switch

If the list of ports is not provided, a Brocade Network Advisor SMI-S agent might not be able to provide the list of ports for a fibre channel switch. The probe completes successfully but does not report that there was a problem. Performance monitor jobs for this switch fail and incorrectly report that a probe of the switch was not run.

If the performance monitoring jobs fail, determine whether the Brocade Network Advisor can communicate with the switch. The Brocade Network Advisor might not be able to communicate with the switch for one of the following reasons:

• There is a problem with the Fibre Channel switch.
• The firmware on the switch might need to be upgraded.

If the Brocade Network Advisor cannot communicate with the switch, contact support for the switch vendor.

If the Brocade Network Advisor can communicate with the switch, contact IBM Software Support.

To resolve the issue, restart the fibre channel switch. This solution is not permanent because the switch might eventually return to this state.

All storage pools are potential candidates for provisioning if you do not specify a storage tier range for a service class

The following text was not included in the online help for service classes:

If you do not specify a storage tier range when you create or modify a service class, all storage pools are potential candidates for provisioning. The storage pools are potential candidates for provisioning, regardless of whether or not they are tagged with a matching tier. To specify a storage tier range, select Storage tier on the Create Service Class wizard or in the properties notebook of an existing service class.

For a storage pool to be considered for provisioning with a specific service class, the pool must fulfil all the requirements of the service class. The requirements include the storage tier range, if one was specified for the service class.

Use the complete file path to the upgradeData.zip file when you migrate reports from Tivoli Common Reporting Version 2.1.1 to Version 3.1.0.1,

When you migrate reports from Tivoli Common Reporting Version 2.1.1 to Version 3.1.0.1, specify the complete path to the upgradeData.zip file.

For example:
/opt/IBM/JazzSM/reporting/bin/trcmd.sh -upgrade -importPackage c:\temp\upgradeData.zip -username smadmin -password xxx

where c:\temp\upgradeData.zip is the complete file path to the upgrade file, and smadmin is the user name that you created when you installed Jazz for Service Management.

Some resources on SAN Volume Controller and Storwize systems temporarily show an incorrect status

The status of internal disks on SAN Volume Controller and Storwize systems is only updated after a probe of the storage system. The status of an internal disk on a SAN Volume Controller or Storwize system might be updated between probes from Tivoli Storage Productivity Center. In this case, the status of the disk in the Tivoli Storage Productivity Center web-based GUI might be temporarily out of date. You can check the status of an internal disk in the SAN Volume Controller and Storwize system user interface.

Directories remain after you uninstall Tivoli Common Reporting

After you uninstall Tivoli Common Reporting, the follow directories are not removed from the C:\Program Files\IBM\JazzSM directory:

• bin
• etc
• lib
• logs
• profile
• reporting
• var

A new IBM SONAS file set might be mistakenly deleted

The file set information was deleted in the other system before the new file set with the existing ID was created."

If Tivoli Storage Productivity Center discovers a new IBM SONAS file set, the ID of a deleted file set might be reused for the new file set. If you delete the older file set in Tivoli Storage Productivity Center, the new file set is deleted instead. This issue occurs in the following circumstances:

• A file set that is known to Tivoli Storage Productivity Center is deleted in a system other than Tivoli Storage Productivity Center.
• Tivoli Storage Productivity Center retained the deleted file set information, either because the probe was not run after the file set was deleted or because the retention period of the file set has not expired.

The file set information was deleted in the other system before the new file set with the existing ID was created.

The prerequisite checker checks the /usr directory instead of the /opt directory

On Linux and AIX operating systems, when you install Jazz for Service Management and Tivoli Common Reporting, instead of checking the /opt directory for free space, the prerequisite checker checks the /usr directory. Ensure that you have sufficient space in the /opt directory.

The web browser becomes unresponsive or a message stating that the script is busy is displayed

If you used the Tivoli Storage Productivity Center web-based GUI to view performance data and charts for an extensive period of time, your web browser might become unresponsive or a message stating that the script is busy might be displayed. You might need to stop and restart your browser. The current performance charts can, in some cases, use more memory than necessary, which can negatively affect browser stability. This issue is addressed in the next release.

The web-based GUI URL is redirected to incorrect ports after an upgrade or an installation

On all operating systems, you are redirected to incorrect port numbers when you start the web-based GUI in the following scenarios:

• After you upgrade from Tivoli Storage Productivity Center Version 4.2.2 to Version 5.2. The correct default port number is 16311, but you are redirected to port 41145.


• After you install Tivoli Storage Productivity Center Version 5.2. The default port number is 9569, but you are redirected to 9563.

The deletion of a large storage system fails due to an error

When you delete a storage subsystem that has a large number of hosts and volumes defined, an error might occur because you exceeded the log file size for the database transaction log during the deletion.

To resolve this issue, you must modify the values for the following DB2 parameter:

DB2 parameter name	Parameter description	Current value	Increase to this value
LOGFILSZ	Log file size	5000	20000
LOGPRIMARY	Number of primary log files	8	100
LOGSECOND	Number of secondary log files	100	150

Restriction: You must ensure there is adequate disk or file system space before you modify the LOGFILSZ, LOGPRIMARY, LOGSECOND parameters. The values in this table will result in approximately 21 GB of log file space. If you have less space available, then use smaller values.

The Virtual Capacity label Storage System Overview chart in the web-based GUI does not match the online help

In the Tivoli Storage Productivity Center web-based GUI, the Virtual Capacity label in the Storage System Details Overview chart does not match the information in the online help. The value that is displayed for Virtual Capacity is the total storage capacity of the volumes in the subsystem pool. The correct name of the label is Total Volume Capacity.

Unable to restart Jazz for Service Management services when Jazz for Service Management is installed without using the Tivoli Storage Productivity Center installation program

On the Windows operating system, if you installed Jazz for Service Management and Tivoli Common Reporting without starting the Tivoli Storage Productivity Center installation program, and you log off or restart your computer, Jazz for Service Management and Tivoli Common Reporting services do not automatically start. You must manually restart the Jazz for Service Management and Tivoli Common Reporting services. For information about restarting Jazz for Service Management and Tivoli Common Reporting services, see Tivoli Storage Productivity Center knowledge center. Search for Starting Tivoli Storage Productivity Center servers.

To resolve this issue, you must install Jazz for Service Management and Tivoli Common Reporting by using the Tivoli Storage Productivity Center installation program.

Restriction: If your computer is part of a Windows domain, to avoid the Access Denied message, you must run the startServer command with the runas parameter.

Discrepancy about the space requirement in the /opt folder to install Jazz for Service Management

Although you need 6 GB in the /opt folder to install Jazz for Service Management, the Prerequisite Scanner check states that you need only 4.6 GB.

To resolve this issue, before you install Jazz for Service Management, ensure that you have at least 6 GB of space in the /opt folder.

The change password tool cannot restart the Device server

When you run the change password tool, the following message is displayed:
There was an error restarting the Device server. Restart the server manually.

To manually start the Device server, follow these steps:

On Windows operating systems:

1. At the command prompt, go to the TPC_installation_directory\scripts directory.
2. Run the stopTPCDevice.bat command.
3. Run the startTPCDevice.bat command.

On AIX or Linux operating systems:

1. At the command line, go to the TPC_installation_directory/scripts directory.
2. Run the ./stopTPCDevice.sh command.
3. Run the ./startTPCDevice.sh command.

Tier and Easy Tier refer to different properties in Tivoli Storage Productivity Center reports

In Tivoli Storage Productivity Center reports, the Storage Virtualizer Pool Tier property refers to the tier that a pool is assigned to in the web-based GUI. The following properties refer to Easy Tier information for SAN Volume Controller and Storwize V7000 systems:

• Storage Virtualizer Pool Tier Capacity
• Storage Virtualizer Pool Tier Available Space
• Storage Virtualizer Pool Tier Number of MDisks
• Storage Virtualizer Tier Type
• Storage Virtualizer Pool Is Easy Tier
• Storage Virtualizer Pool Easy Tier Status

The Status column on the Storage Systems page might show a status of Normal when the initial probe fails for a storage system

After you run a probe on a storage system for the first time, the Status column on the Storage Systems page might incorrectly show a status of Normal when the probe fails. The Status column on the Pools page also might show a status of Normal for pools that are configured in the storage system. The Probe Status column on the Storage Systems page correctly shows a status of Failed.

Data that was collected by the probe before the error occurred is saved in the database and is incorrectly included in the Available Pool Space value on the Pools page and the Available Space value on the Service Class page.

To fix this problem, resolve the issue that caused the probe failure and run the probe again for the storage system. You can view the error message in the logs for the probe run.

The Pool Performance table incorrectly displays the pool status as unreachable after the initial probe

In some cases, the status of a pool displays in the Pool Performance table as unreachable after the initial probe of the device. The status of the pool displays correctly in the Pools page. To resolve the incorrect status, wait approximately 10 minutes and run the probe again.

An incorrect icon is displayed for thin-provisioned volumes

On the User Task Provisioning panel, when you create a thin-provisioned volume, the icon for a normal volume is displayed instead. To resolve this issue, click the link to the related ServiceClass to verify the type of volume that will be created.

Storage Resource agent probe jobs remain in the Running state and the logs display a status of In progress

On HP-UX operating systems, when you run a probe on Storage Resource agents that have Network Attached Storage (NAS) exports mounted on them, the probe job crashes and the logs continue to display an In progress status. This issue also occurs when you upgrade the server.

To resolve this issue, if you plan to run a probe, do not mount NAS exports on HP-UX operating systems.

The documentation does not completely describe why a SAN Volume Controller can be eliminated as a provisioning candidate

When you request storage volumes, a SAN Volume Controller that already has the maximum number of volumes that are allowed for each I/O group is eliminated as a candidate for provisioning. If a location for the requested volumes cannot be found, an error message indicates only that there is not enough available storage. If a SAN Volume Controller satisfies the service class and capacity requirements of a provisioning request, but is not being used for storage placement, it might be because it already has the maximum number of volumes allowed. Check the SAN Volume Controller to verify that the maximum number of volumes for each I/O group is not reached.

Inconsistency between the Fabrics page and the Fabrics details page

In the web-based GUI, when you probe for a Storage Resource agent that is connected to a fabric, and you disable the fabric function, the Storage Resource agent's Update Credentials menu option will only be available from the Fabric page, and not the Fabric details page.

To update the credentials, on the Fabrics page, click Connection > Update Credentials.

Error when logging in to the web-based GUI when DB2 is not running

On Linux operating systems, if you reboot the computer on which Tivoli Storage Productivity Center is installed, DB2 might not start automatically. As a result, you cannot log in to the web-based GUI. To resolve this issue, before you log in to the web-based GUI, you must manually stop and restart all the Tivoli Storage Productivity Center services. For information about setting up the automatic starting of DB2 services on Linux and UNIX, see the Tivoli Storage Productivity Center knowledge center. Search for DB2 services and select this topic: DB2 services do not start when you restart the system on a UNIX platform.

The IP address or fully qualified domain name of a data source is displayed twice on the Connections menu

The IP address or fully qualified domain name (FQDN) of a data source for a fabric or switch might appear twice on the Connections menu. This issue can occur when you right-click a fabric or switch, and then click Connections > Test Connection or Connections > Update Credentials. For example, you have a switch with the IP address 192.0.2.1, which has a CIMOM data source and an SMNP data source. When you click Connections > Test Connection, you see two 192.0.2.1 menu items, one for each of the data sources.

This issue occurs if both data sources are on the same server and are both configured with the IP address or FQDN. To see which data source the menu item is for, click one of the menu items. The data source is displayed on the page that is displayed.

Selected volumes in the Volumes Historical Capacity report are not removed if you change storage system

After you run a report, you can click the Run Report icon to run the report again. In the Volumes Historical Capacity report, if you click Run Report and then change the storage system, the volumes that you selected previously are not removed.

To resolve the issue, complete one of the following tasks:

• Select the volumes and remove them.
• Click Cancel and then run the report again.

The chart on the Volumes Capacity report shows only one capacity value

Unlike other predefined reports about capacity, the Volumes Capacity report shows only one capacity value. The capacity and allocated space of the volume is not displayed on the chart. To see the capacity and allocated space, view the Storage Volume Capacity and Storage Volume Allocated Space columns in the report table.

Information about migrating data collections jobs is incorrect in the online help

Some text in the Data collection topic of the online help for the web-based GUI is incorrect. For more information about the correct text, see the doc_corrections PDF attachment.

Information about removing an expired certificate is missing from the Enabling secure communication between Tivoli Storage Productivity Center and the LDAP repository information center topic

In the Enabling secure communication between Tivoli Storage Productivity Center and the LDAP repository information center topic, steps are missing after step 6.

For information about the missing steps, see the doc_corrections PDF attachment.

The Network action on the Provisioning detail page has a status of Warning if the zone exists

The provisioning task includes an action to create a zone between a storage system and a host. When the provisioning task runs, the zone is not created because the zone exists.

It is likely that another provisioning task created the zone. The status of the Network action is set to Warning and the overall status of the provisioning task is also set to Warning. However, this warning does not prevent the provisioning task from completing the remaining provisioning actions.

You can view detailed information in the logs for the provisioning task about why the zone was not created.

The Tivoli Storage Productivity Center installation wizard can loop when you install Tivoli Common Reporting

The installation wizard can loop if you skip the installation of Tivoli Common Reporting, proceed to the Pre-Installation Summary page, and then return to the Welcome page to install Tivoli Common Reporting. After you enter the correct authentication information on the Configure Jazz for Service Management and Tivoli Common Reporting page, the wizard returns you to the Single Server Installation Information page instead of proceeding to install Tivoli Storage Productivity Center with reports.

The wizard is in a loop and you cannot complete the installation of Tivoli Storage Productivity Center.

To install Tivoli Storage Productivity Center with Tivoli Common Reporting, cancel the wizard and restart the installation.

Some characters might not be displayed correctly in reports in PDF format

Characters from the Mongolian, Tibetan, or Yi languages are displayed as square boxes in reports in PDF format. To resolve this problem, you must enable IBM Cognos to display Chinese characters correctly. For more information about how to enable IBM Cognos to display Chinese characters correctly, see the IBM Cognos Business Intelligence 10.2.0 information center. Search for Chinese characters.

Running multiple optimization recommendations at the same time results in a Pool Exhaustion Exception error

In some cases, running more than 15 optimization recommendations at the same time can cause one or more of the individual recommendation executions to result in a Pool Exhaustion Exception error. This can be caused by a lack of available resources in the operating system thread pool. You can manually complete the failed recommendations.

If this situation occurs frequently, contact IBM Support for assistance in reducing the number of concurrently running optimization recommendations.

A provisioning request for the DS8000 system fails when insufficient free volume IDs are available

When you specify a provisioning request to create multiple volumes on a DS8000 system that does not have enough free volume IDs on the even or odd logical subsystems (LSS) to fulfill the request, the remaining volumes are not created.

To resolve this issue, do not specify more than the available LSS volumes when creating a
provisioning request to create volumes on a DS8000 system.

The value for the Storage Pool Physical Allocation Percentage property is incorrect in reports

The value for the Storage Pool Physical Allocation Percentage property is incorrect in Tivoli Storage Productivity Center reports. To see the correct value for a pool, view the pool in the web-based GUI. The physical allocation percentage is displayed in the Physical Allocation column.

The provisioning wizard shows capacity in MB, GB and TB instead of MiB, GiB, and TiB

The Capacity field of the provisioning wizard incorrectly shows the volume capacity attribute in MB, GB, and TB. The correct volume capacity attribute is MiB, GiB, and TiB. This will be fixed in a future release of Tivoli Storage Productivity Center.

The Zero Buffer-Buffer Credit Percentage Threshold condition is missing from the Triggering Condition list

In the Tivoli Storage Productivity Center stand-alone GUI, on the Create Storage Subsystem window, when you try to create a storage subsystem alert, the Zero Buffer-Buffer Credit Percentage Threshold option is missing from the Triggering Condition list.

Tip: If the Zero Buffer-Buffer Credit Percentage Threshold condition had existed, this data would be displayed in the performance metrics reports for storage virtualizer ports.

The Zero Buffer-Buffer Credit Timer is included in the list. When you select this triggering condition, the Zero Buffer-Buffer Credit Timer information is displayed in the performance metrics reports for storage virtualizer ports, systems, nodes, and I/O groups.

A successful test of the connection does not change the device status from Unreachable to the actual status of the device

In some cases, when you click Test Connection on a specified device that is unreachable, the device status is not changed. To resolve this condition, run a probe on the device or wait until the next scheduled probe completes for that device.

The installation fails because the TPCDB database cannot be created

If Tivoli Storage Productivity Center was installed several times on a system, a new installation might fail when it tries to create the TPCDB database. This problem occurs because the TPCDB database from the previous installations is not removed.

To resolve this issue, complete the following steps:

1. If the TPCDB directories exist in the system database directory, delete the TPCDB directories.

2. Run the following commands:

db2 catalog database TPCDB
db2 drop database TPCDB

3. Restart the installation.

No error message is displayed if you assign a duplicate port to a server

In the Assign Ports page on the Add Server wizard, you assign the number of a WWPN for the server. If you type the number of a WWPN that exists and then click Add, the WWPN is not added, and no error message is displayed.

To resolve this issue, click Add again, and the error message is displayed. To remove a port from the list, click the Cancel icon next to the port.

Some files are not added to the custom directory if the service tool specifies the output option

On AIX operating systems, when you run the service tool, you cannot automatically collect host, version, or license files when you use a custom directory. To resolve this issue, do not run the service tool with the -output custom_dir option.

Some folders are not removed when you upgrade to Tivoli Storage Productivity Center Version 5.2 and then uninstall Version 5.2

After you upgrade from Tivoli Storage Productivity Center Version 4.2.2.4 to Version 5.2, if you uninstall Version 5.2 and restart the computer, some folders are left behind in the C:\Program Files\IBM\TPC directory. Also, the Tivoli Storage Productivity Center for Replication icon is displayed in the "Uninstall or change a program" window. When you try to uninstall Tivoli Storage Productivity Center for Replication, a message stating that Tivoli Storage Productivity Center for Replication has been uninstalled is displayed in the Control Panel window.

To resolve this issue, you must manually delete the TPC folder from the installation directory.

Tivoli Storage Productivity Center server shows two different fully qualified host names

If a Tivoli Storage Productivity Center server uses one DNS server and another server which has a Storage Resource agent installed that uses a different DNS server, the Tivoli Storage Productivity Center server might be displayed in some web-based GUI pages with different fully qualified host names. This is because the Tivoli Storage Productivity Center server is identified by two different DNS servers.

Some comparison reports do not show volumes or ports from NetApp devices

The following reports do not show volumes or ports from NetApp devices:

• Compare Performance of Multiple Volumes
• Compare Performance of Multiple Ports

You can run the Performance of One Volume or Performance of One Port report to create a report for each device that you want to compare. Then, you can manually compare the performance.

Alternatively, you can use Query Studio to compare devices across multiple NetApp volumes. However, you cannot compare volumes from other device types, such as DS8000, SAN Volume Controller, and XIV systems.

Information is missing in the Adding an LDAP repository to the federated repositories information center topic

For more information about the missing text, see the doc_corrections PDF attachment.

A hypervisor probe job fails with no error message

In some cases, a hypervisor probe job might fail with no error message in the log. You can try to resolve the issue by examining the traceTPCDeviceServer*.log files.

The Jazz for Service Management prerequisite checker fails on Red Hat Enterprise Linux Version 5.6 installation because the required library is not found

During the Tivoli Storage Productivity Center Version 5.2 installation, the Jazz for Service Manager installation program on Red Hat Enterprise Linux Version 5.6 searches for the /lib/libz.so.1 file and fails if this file is not found.

To resolve this issue, complete these steps:

1. Edit the Tivoli Common Reporting configuration file:

/<download_location>/JazzSM/PrereqScanner/UNIX_Linux/TCR_03010001.cfg.

2. Locate the following line:

[OSType:RedHatEnterpriseLinuxServer5.*]
os.lib.libz.so.1_32=/lib/libz.so.1

3. Change the line to this text:

os.lib.libz.so.1_32=/usr/lib/libz.so.1

4. Save the configuration file, and restart the installation process.

Some hyperlinks in the VMware vSphere web client do not work correctly when using Google Chrome

When using the Google Chrome Version 29 browser, some hyperlinks from the vSphere web client to the Tivoli Storage Productivity Center web-based UI result in a This web page is not available error. This is caused by the browser not handling certificates properly.

To resolve this issue, refresh the browser window. This will cause the browser window to display the Certificate not trusted window. Click Proceed anyway to continue to the Tivoli Storage Productivity Center web-based GUI.

Documentation is available to upgrade a DB2 server on Linux or UNIX operating systems

Documentation for upgrading a DB2 server on a Windows operating system is included in the Tivoli Storage Productivity Center information center and IBM Tivoli Storage Productivity Center Version 5.2 User's Guide. For documentation about how to upgrade a DB2 server on a Linux or UNIX operating system, see the IBM DB2 Version 10.1 information center. Search for Upgrading a DB2 server (Linux and UNIX).

Unable to run Tivoli Storage Productivity Center reports when you upgrade from Tivoli Storage Productivity Center Version 5.1.1.2 to Version 5.2 on AIX operating systems

On AIX operating systems, before you upgrade from Tivoli Storage Productivity Center Version 5.1.1.2 to Version 5.2, verify whether Tivoli Storage Productivity Center reports work. If reports do not work, some of the files that were bound to DB2 may have been deleted. If this occurs, you cannot run Tivoli Storage Productivity Center reports.

Restriction: You must complete the following procedure before you upgrade to Tivoli Storage Productivity Center Version 5.2. After you complete the procedure, verify that you can run Tivoli Storage Productivity Center reports, and then upgrade to Tivoli Storage Productivity Center Version 5.2.

To resolve this issue, complete the following steps:

1. Log in to Tivoli Storage Productivity Center by using the root user name.
2. At the command line, issue the following commands:

su - db2inst1
db2 terminate
db2 connect to tpcdb
db2 bind /opt/IBM/db2/V9.7/bnd/db2schema.bnd blocking all grant public sqlerror continue
db2 terminate

The Device sever might be unavailable after you install Tivoli Storage Productivity Center Version 5.2

After you install Tivoli Storage Productivity Center 5.2, the Device server might be unavailable. This issue might occur immediately after you install Tivoli Storage Productivity Center or at a later time. To resolve this issue, you must manually restart the Device server. For information about restarting the Device server, see the Tivoli Storage Productivity Center knowledge center. Search for Starting the Tivoli Storage Productivity Center servers.

The Start Probe action might not be available on the Servers page after you upgrade from Tivoli Storage Productivity Center Version 4.2.2 to Version 5.2

The Start Probe action might not be available on the Servers page after you upgrade to Tivoli Storage Productivity Center Version 5.2. The Start Probe action is correctly available for the server on the Server details page.

To start a probe run for a server, use the Start Probe action on the Server details page. After the probe run completes, the Start Probe action is available for the server on the Servers page.

Cannot modify the data collection schedule for some performance monitor jobs after you upgrade

If you upgrade to Tivoli Storage Productivity Center Version 5.2, you might not be able to modify the data collection schedule for some performance monitor jobs. This issue is related to the job schedule IDs that are generated in Tivoli Storage Productivity Center. When you try to modify the schedule, the following message is displayed:

The schedule for collecting status and asset data cannot be created.

The Performance tab is displayed for storage system disks for which performance information is not supported

The server details page in the web-based GUI shows information about server-related resources, including storage system disks that are associated with the volumes that are assigned to the server. A Performance tab shows performance information for SAN Volume Controller, Storwize V7000, and Storwize V7000 Unified storage virtualizers.
Although performance information for disks is available only for these storage virtualizers, the Performance tab might be displayed for other storage systems. The Performance tab cannot show disk information for other storage systems.

Cannot view details or data collection for unmanaged filers

Filers that are not managed by Tivoli Storage Productivity Center are displayed on the File System tab of the Storage Systems page in the web-based GUI. However, you cannot view detail or data collection information for these filers.

Cannot access Tivoli Storage Productivity Center reports after using the change password tool to change the DB2 password

If the DB2 user name that you entered when you installed Jazz for Service Management and Tivoli Common Reporting is different from the DB2 user name that you entered when you installed Tivoli Storage Productivity Center, you cannot access Tivoli Storage Productivity Center reports.

To resolve this issue, see the Jazz for Service Management Version 1.1.0.1 information center. Search for Content Store setting in Cognos Configuration.

Unable to add storage subsystems by using an IPv6 address

You cannot add a storage subsystem by entering the IPv6 address into the Host name or IP address field.

To resolve this issue, update the setting in the database table by entering the following SQL database statements:

update the t_res_config_data set value='false' where attribute='TestConnection.verifyReachabilityViaICMP'.
commit

Information center topic incorrectly lists embedded TPC as a valid license type

In the IBM Tivoli Storage Productivity Center Installation and Configuration Guide, the Adding an installation license topic states that an embedded version of Tivoli Storage Productivity Center is available as part of IBM® Systems Director. This is not correct for Tivoli Storage Productivity Center Versions 5.1 and later.

APAR IC99541: Error message BPCUI0292E has been updated

The explanation and action sections of this message have been updated:

Explanation
The Tivoli Storage Productivity Center server is unable to contact the IP address or host name of the resource. This problem might occur if the local area network is down, the ping (ICMP) command is failing, or a firewall is preventing communication between the server and the resource.

Action
Verify that the IP address or host name of the resource is valid. Verify that the local area network is available. Verify by using the ping (ICMP) command that the resource is reachable from the
TPC server. Ensure that a firewall is not preventing network access. Ensure that the Tivoli Storage Productivity Center server is running properly. Try to add the resource again.

To track the status and resolution of this APAR, see http://www.ibm.com/support/docview.wss?uid=swg1IC99541.

Limitations and known issues when using Tivoli Storage Productivity Center with VMware vSphere

The following limitations and known issues can occur when you use Tivoli Storage Productivity Center with VMware vSphere:

vCenter Server does not display events from the Tivoli Storage Productivity Center VASA provider

The SMS log might show that events were received from the Tivoli Storage Productivity Center VASA provider and an attempt was made to post them to the vCenter Server.

In the vSphere Client, click Home > Management > Events. The event from the VASA provider is not logged. In the vSphere Web Client, click Home > Monitoring > Event Console. The event from the VASA provider is not displayed.

Storage DRS calls fail for datastore clusters with file system storage

When a Tivoli Storage Productivity Center VASA provider is added to the vCenter Server, a datastore cluster that contains a NetApp datastore and an IBM® Scale Out Network Attached Storage datastore fails to log Storage DRS calls.

vCenter Server does not send a storage DRS request to the Tivoli Storage Productivity Center VASA provider

In a datastore clustered NFS environment, vCenter Server does not send a Storage DRS request to the Tivoli Storage Productivity Center VASA provider. System Capability and Storage Provider Namespace values are populated correctly.

Tivoli Storage Productivity Center VASA provider alarms might be displayed in the Events panel

Tivoli Storage Productivity Center alerts that are sent as alarms to the vCenter Server from the Tivoli Storage Productivity Center VASA provider might be displayed in the Events panel, instead of the Alarms panel.

Tivoli Storage Productivity Center VASA provider SpaceCapacity alarm might behave inconsistently

If a VASA SpaceCapacity alarm is return to a LUN that does not belong to a datastore, an event is displayed in the vCenter Server. If the LUN belongs to a datastore, two non-relevant events are displayed.

Alerts omit the storage provider name

In the vSphere Client, the Events tab shows the Storage provider name that is associated with an alert. In the vSphere Web Client, the Events Console omits the Storage provider name.

Alarms with the StorageFileSystem entity type are flagged as unknown

For the Tivoli Storage Productivity Center VASA provider alarms on StorageFileSystem objects that are returned to the vCenter Server, an unknown vCenter identifier is displayed.

Delay in refreshing Tivoli Storage Productivity Center VASA provider data in Storage Reports after synchronization

VASA provider data can take some time to be displayed in Storage Reports after a successful synchronization.

The data format limitation and ESS LUN cannot be correlated by vCenter Server

With some storage subsystems, such as IBM Enterprise Storage Server® (ESS), Hitachi, and NetApp, there are potential limitations in display name values and information currency.

With Hitachi and NetApp systems, the format that is used on the vCenter Server might be NAA. When Hitachi and NetApp systems are probed by Tivoli Storage Productivity Center, depending on the CIMOM versions, the names that are returned use either the T10 or the NAA format.

With ESS, the CIMOM returns the names of LUNs by using the NAA format, while vCenter Server uses the T10 format.

In these cases, the vCenter Server cannot correlate the data that is returned by the Tivoli Storage Productivity Center VASA provider, and the reports are not populated with the data from Tivoli Storage Productivity Center. A potential workaround is to probe the hypervisor to obtain the correct name to use. This technique resolves the name if it uses either the T10 or the NAA format.

To obtain the correct name by probing the hypervisor, the probe must complete successfully. If the probe of the hypervisor can only populate some of the data, the LUN data that is returned by Tivoli Storage Productivity Center VASA provider persists to the data that is obtained from the CIMOM. This limitation might cause the vCenter Server correlation to fail.

The Volume Not Found alert might not be displayed in vCenter Server

The vCenter Server SMS log shows a generated alert, but the alert is not displayed on the vSphere Client or the vSphere Web Client.

The Storage Array column does not display Hitachi system names

Some Hitachi system names are not displayed on the vSphere SCSI Volume (LUNs) report under the Storage Array column.

The Tivoli Storage Productivity Center VASA provider does not register automatically on vCenter Server

When an exception occurs while querying an existing Tivoli Storage Productivity Center VASA provider by using the Storage Monitoring Service API, the automatic registration of the VASA provider may not succeed.

Storage View reports on vCenter Server take a long time to refresh

If you configure VASA providers on the vCenter Server, it might take a long time for the Storage View reports to refresh. This issue is more likely to occur if you have more than one VASA provider configured.

As a workaround, configure only one VASA provider on the vCenter Server.

The vSphere Web Client extension recovery after the vSphere Web Client server restarts

A vCenter Server provisioning task might stay in a Queued state during the approval process by the Tivoli Storage Productivity Center administrator. During this time, the vSphere Web Client server or the host machine might be restarted.

The vSphere Web Client can close a connection to the vCenter Server after a timeout. The default for this timeout is 120 minutes.

If a timeout occurs, the vSphere Web Client extension for Tivoli Storage Productivity Center restores the connectivity to the vCenter Server and Tivoli Storage Productivity Center when a user logs in to the vSphere Web Client. The status of the provisioning task is updated based on the status of the task in Tivoli Storage Productivity Center.

To start the recovery process, log in to the vSphere Web Client and go to one of the following panels in the vSphere Web Client extension:

• Tivoli Storage Productivity Center provisioning
• Tivoli Storage Productivity Center saving configuration information
• Tivoli Storage Productivity Center storage system metrics

The All TPC Actions string is not translated in some locales

Due to an error in the translation process, the All TPC Actions string is not translated in double-byte locales.

Display a more meaningful error message in logs when you try to provision storage when the Data server is down

If you try to use the vSphere Web Client extension for Tivoli Storage Productivity Center to provision storage when the Data server is not running, the provisioning task fails.

The following error message is displayed:

TPC could not provision storage. Check the TPC plugin files.

To prevent this issue from occurring, ensure that all Tivoli Storage Productivity Center services are up and running.

The Tivoli Storage Productivity Center VASA provider status is displayed as Rescan Error

If there is a space in the name of a service class, the VASA provider synchronization fails. The VASA provider status changes to Rescan Error.

To resolve this issue, remove the space in the service class name and rescan the VASA provider.

If this error occurs when Tivoli Storage Productivity Center is registered as a VASA provider, you must unregister the VASA provider and register it again.

Storwize V3500 and V3700 are not referenced in the reporting documentation for the stand-alone GUI

Reports that are available for Storwize V7000 in the Tivoli Storage Productivity Center stand-alone GUI are also available for Storwize V3500 and Storwize V3700. Where Storwize V7000 is specified for a report in the "Reporting in the stand-alone GUI" section of the Tivoli Storage Productivity Center information center and the IBM Tivoli Storage Productivity Center Version 5.2 User's Guide, Storwize V3500 and Storwize V3700 are also supported.

Error SRV0853E is displayed when you try to log in to the stand-alone GUI

In some cases, when you try to log in to the stand-alone GUI, you get a SRV0853E error message. You see an error similar to the following error in the Data Server log file (<TPC_installation_directory>\data\log\ServerTrace.log):

2016-10-18 13:14:23.931+0200 EXCEPTION
  java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy5.authenticate(Unknown Source)
at com.tivoli.itsrm.server.SingleSignonHndlr.authenticateUserOrToken(SingleSignonHndlr.java:409)
at com.tivoli.itsrm.server.SingleSignonHndlr.handle(SingleSignonHndlr.java:141)
at com.tivoli.itsrm.server.RequestManager$RmThread.run(RequestManager.java:501)
Caused by: [SOAPException: faultCode=SOAP-ENV:Server; msg=java.lang.IllegalArgumentException: Illegal daylight saving value: 0]
at org.apache.soap.providers.RPCJavaProvider.invoke(Unknown Source)
at com.tivoli.sanmgmt.middleware.data.RPCSecureJavaProvider.invoke(RPCSecureJavaProvider.java:172)
at org.apache.soap.server.http.RPCRouterServlet.doPost(Unknown Source)
at com.tivoli.sanmgmt.middleware.TSNMServiceManager.doPost(TSNMServiceManager.java:469)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1275)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:766)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:472)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1101)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:81)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:912)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:262)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:938)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:798)  com.tivoli.itsrm.server.RequestManager$RmThread run RequestHandler0

This error occurs because the Java Runtime Environment (JRE) does not comply with Daylight Saving Time (DST). To fix this problem, do one of the following actions:

• Change the time zone to comply with JRE. Use the time zone data versions web page at http://www.oracle.com/technetwork/java/javase/tzdata-versions-138805.html to identify a time zone that complies with JRE.
• Update the JRE to make it comply with DST. Oracle provides a TZUpdater tool that you can use to update JRE with more recent time zone data, including DST changes in different countries. For more information about the TZUpdater tool, see http://www.oracle.com/technetwork/java/javase/documentation/tzupdater-readme-136440.html.