IBM Support

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

Preventive Service Planning


Abstract

This document provides information about limitations and known issues that you might encounter when you use IBM® Tivoli® Storage Productivity Center Version 5.2.3 or Tivoli® Storage Productivity Center for Replication Version 5.2.3.

Content

To access all of the support documentation, including alerts and APARs, go to the IBM Support Portal.


For the list of limitations and known issues for Tivoli Storage Productivity Center V5.2.2, see http://www.ibm.com/support/docview.wss?uid=swg21671119.

For a list of the known issues with the Tivoli Storage Productivity Center support for Hitachi Data Systems Virtual Storage Platform, see http://www.ibm.com/support/docview.wss?uid=swg21667294.

For information about the devices that are supported by Tivoli Storage Productivity Center, 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.3 Quick Installation Guide and other publications, see the printable documentation download web site at ftp://public.dhe.ibm.com/software/tivoli/tpc/v523/.

The IBM Tivoli Storage Productivity Center V5.2.3 Knowledge Center is available here: http://www.ibm.com/support/knowledgecenter/SSNE44_5.2.3/com.ibm.tpc_V523.doc/tpc_kc_homepage.html.

Product licenses for Tivoli Storage Productivity Center

Tivoli Storage Productivity Center V5.2.3 offers product licenses with differing functionality to meet your storage management needs. For information about these licenses, see http://www.ibm.com/support/knowledgecenter/SSNE44_5.2.3/com.ibm.tpc_V523.doc/fqz0_r_product_packages.html.

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.

Documentation update: DS8000 storage system default ports

In table 2 of the Tivoli Storage Productivity Center for Replication for System z knowledge center topic Ports, the System Storage DS8000 should include two default ports: 1750 and 1751. For more information, see the support topic for APAR IT0913 http://www-01.ibm.com/support/docview.wss?uid=swg1IT01913.

You can navigate to this Knowledge Center topic by using this path:
Tivoli Storage Productivity Center for Replication for System z 5.2.3>Product overview>Key concepts>Ports.


Upgrade TCRDB when upgrading DB2 from 32-bit DB2 Version 9.7 to 64-bit DB2 Version 10.1

When you upgrade to Tivoli Storage Productivity Center V5.2 or later, you must also upgrade DB2 from 32-bit Version 9.7 to 64-bit 10.1. During the DB2 upgrade, you must upgrade both the TPCDB and TCRDB databases. If you do not upgrade TCRDB when you upgrade TPCDB, you might see this error in the TPC_installation_directory\TPC\logs\traceTPCInstall.log file:

com.ibm.tpc.install.frontend.ia.actions.CheckJazzSMTCRandCognosAction install Error - TCR is not reachable

You can see instructions for upgrading the TPCDB and TCRDB databases during the DB2 upgrade in this Knowledge Center topic: Upgrading from 32-bit DB2® Version 9.7 to 64-bit DB2 Version 10.1 at http://www.ibm.com/support/knowledgecenter/SSNE44_5.2.3/com.ibm.tpc_V523.doc/fqz0_t_upgrading_db2.html.


TCP/IP ports used by Tivoli Storage Productivity Center: Knowledge Center topic update

The Knowledge Center topic TCP/IP ports used by Tivoli Storage Productivity Center should specify that port 1751 is the default port used by Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication to communicate with DS8000 devices. Port 1750 is used if port 1751 is unavailable. Currently this topic only identifies port 1750 as the communication port. This topic has been updated in a later release of the Knowledge Center.



Documentation update for online help topic Storage System Internal Resources

The Volume Status description in this help topic has been updated to include a description of Syncing status:

    Status
    The status of a volume. Statuses include Normal, Warning, Error, Unknown, Online, Offline, Syncing, Degraded, Excluded, and Unreachable. Use the status to determine the condition of the volume, and if any actions must be taken. For example, if a volume has an Error status, take immediate action to correct the problem. Syncing status indicates that a SAN Volume Controller or Storwize V7000 volume is part of a mirrored pair and is in the process of synchronizing with the primary volume. Syncing status will change when a subsequent probe detects a status change in the volume.


APAR IT06215: Uninstalling the Deployment Engine

The Knowledge Center and Installation Guide topic Uninstalling Tivoli Common Reporting and Jazz for Service Management does not contain information about how to remove the Deployment Engine, which is a component of Tivoli Common Reporting. For instructions about how to remove the Deployment Engine, see http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tcr_original/ttcr_uninstal_manually.html.

You can see the status of this APAR here: http://www.ibm.com/support/docview.wss?uid=swg1IT06215

Documentation correction for topic Planning for Brocade, QLogic, or Cisco fabric management agents

Topic title: Planning for Brocade, QLogic, or Cisco fabric management agents

This topic incorrectly states that the supported interface for performance monitoring for Brocade and Cisco fabrics is an SMI agent. Tivoli Storage Productivity Center supports CIM agents and SNMP agents for Brocade and Cisco fabrics. This topic appears in both the Knowledge Center and the Installation Guide.

Documentation correction for topic Planning for storage systems

Topic title: Planning for storage systems

This topic incorrectly states that Tivoli Storage Productivity Center supports storage provisioning for GPFS™ clusters and GSS systems. Tivoli Storage Productivity Center supports asset reporting and capacity reporting for GPFS clusters and GSS systems. Storage provisioning is not currently supported for these systems. This topic appears in both the Knowledge Center and the User's Guide.

Performance Metrics topic is missing from V5.2.3 Knowledge Center

The topic Performance Metrics is missing from the latest Tivoli Storage Productivity Center Knowledge Center. The topic is attached here in PDF format.

TPC_reporting_performance_metrics.pdfTPC_reporting_performance_metrics.pdf

Documentation update: Performance metrics available for pools and managed disks in SAN Volume Controller and Storwize V7000 systems

The Knowledge Center topic Performance metrics is missing information about the performance metrics that are available for pools and managed disks that are in SAN Volume Controller and Storwize V7000 systems.

The following metrics are available when you view the performance of pools in SAN Volume Controller and Storwize V7000 systems:
* Read Cache Hits Percentage (overall)
* Write Cache Hits Percentage (overall)
* Total Cache Hit Percentage (overall)
* Disk to Cache I/O Rate
* Cache to Disk I/O Rate
* Write Cache Delay Percentage
* Write Cache Delay I/O Rate
* Read Ahead Percentage of Cache Hits
* Dirty Write Percentage of Cache Hits
* Write Cache Overflow Percentage
* Write Cache Overflow I/O Rate
* Write Cache Flush-through Percentage
* Write Cache Flush-through I/O Rate
* Write Cache Write-through Percentage
* Write Cache Write-through I/O Rate
* Global Mirror Write I/O Rate
* Global Mirror Overlapping Write Percentage
* Global Mirror Overlapping Write I/O Rate
* Global Mirror Secondary Write Lag
* Peak Read Response Time
* Peak Write Response Time
* Overall Host Attributed Response Time Percentage

The following metrics are available when you view the performance of managed disks on SAN Volume Controller and Storwize V7000 systems:
* Back-end Read I/O Rate
* Back-end Write I/O Rate
* Total Back-end I/O Rate

Support for Storwize V5000

Tivoli Storage Productivity Center provides data storage management for the IBM Storwize V5000 storage system. Tivoli Storage Productivity Center features that are available for the IBM Storwize family are also available for Storwize V5000 except where noted in the documentation.

Relationships between resources and fabrics and switches are not displayed correctly in report

If you select Reporting > Create capacity reports in the web-based GUI, you can create custom reports about capacity and relationships. The Capacity and Relationships package in Tivoli Common Reporting contains a new Fabrics and Switches folder. If you create a custom report that includes properties from both the Servers to Storage Systems folder and the Fabrics and Switches folder, the relationships between resources are not displayed correctly.

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

On some IBM servers running Windows 2012, an enabled ethernet port can cause the Tivoli Storage Productivity Center web-based 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 Tivoli Storage Productivity Center web-based GUI to stop responding.

To prevent this, disable the ethernet port or configure the port by using the instructions here: 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.


Unexpected behaviors occur in the Tivoli Storage Productivity Center for Replication GUI
When you upgrade to Tivoli Storage Productivity Center for Replication Version 5.2.x, behaviors such as these might occur on the GUI pages:
  • The page is loading for a prolonged amount of time.
  • The page is partially rendered.
  • Buttons and other items on the page do not work.
  • Images are missing from the page.
If these behaviors occur, clear the cache for the web browser in which the Tivoli Storage Productivity Center for Replication GUI is running. For instructions on how to clear the cache for a specific browser, refer to the documentation for that browser.

GPFS/GSS systems are not correctly represented in the stand-alone GUI


You might experience the following types of issues related to GPFS/GSS support:
  • GPFS/GSS systems are not correctly represented in the Topology Viewer of the stand-alone GUI.
  • GPFS/GSS systems are incorrectly displaying in the stand-alone GUI in several Data Manager panels, including Data Manager>Reporting>Asset>By Computer and Data Manager>Reporting>Asset>By Storage Subsystem.
  • GPFS/GSS file systems are not correctly represented in Cognos reports that are included with Tivoli Storage Productivity Center.
  • Information about NFS and CIFS exports that are defined on a GPFS/GSS cluster is not collected.
  • From the Alerts page in the web-based GUI, selecting a Resource Link from the File System Not Found alerts table opens the properties notebook for that resource, and displays error BPCUI0000E. Also, in some cases clicking on File Set in the Alerts table will display the File System properties notebook. Other unexpected behavior can occur from the web-based GUI Alerts pages.

Error message BPCIN0224E is displayed during the pre-installation of Tivoli Storage Productivity Center on a Windows domain

If you specify a domain user account for the common user when you install Tivoli Storage Productivity Center, but a local user account was created during the DB2 installation, the following error message is displayed:
    BPCIN0224E The user Domain Name\Domain User is a domain account and cannot be used to log in to DB2. You must enter a separate user name for DB2.
This error occurs when you click Next in the Single Server Installation Information page of the installation wizard.

To resolve this error:

1. Click Configure Database repository in the Single Server Installation Information page.
2. In the Configure the Database Repository page, enter the DB2 user name without a Windows domain name prefix, enter the password for the DB2 user, and click Validate.
3. When the validation is complete, click OK to exit the Configure the Database Repository page and return to the Single Server Installation Information page.
4. Click Next on the Single Server Installation Information page to continue the installation.

Error messages BPCIN0057E and BPCIN0072E are displayed during the pre-installation of Tivoli Storage Productivity Center on Linux systems

In rare occurrences, the Tivoli Storage Productivity Center installation program cannot validate the DB2 db2inst1 user during pre-installation on a Linux system and the following error messages are displayed:

    BPCIN0057E The user name db2inst1 is not in an operating system group that has DB2 SYSADM authority.

    BPCIN0072E The validation for user name db2inst1 has failed. Check to see if this user name exists or if DB2 is running.

These messages are generated during a pre-installation check and are displayed at the beginning of the installation process

These messages might be displayed erroneously. Determine whether the DB2 db2inst1 user has SYSADM authority and that DB2 is running. If the user has the correct authority and DB2 is running, cancel the installation and start the installation program again.

If the db2inst1 user does not have SYSADM authority or DB2 is not running, correct the problem and then continue the installation.

Disable Windows User Account Control to edit configuration files

On Windows installations, if you installed Tivoli® Storage Productivity Center by using a domain user account, you must disable User Account Control to edit the Tivoli Storage Productivity Center configuration files.

Incorrect link in Troubleshooting Jazz for Service Management installation procedure topic

In the online product documentation for Tivoli Storage Productivity Center, the Troubleshooting Jazz for Service Management installation procedure topic contains an incorrect link to the Jazz for Service Management documentation. The following link goes to the correct URL:

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/ref/psc_r_install_smsetappserver_cmd.html

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 Version 1.1.0.3
    • Tivoli Common Reporting Version 3.1.0.1
    • Tivoli Common Reporting Version 3.1.0.2
    • IBM WebSphere Application Server Version 8.5.0.1
  • 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 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

When you install Jazz for Service Management, you must use the Tivoli Storage Productivity Center installation program. If you do not use the Tivoli Storage Productivity Center installation program, you will experience the following types of issues:
  • The Jazz for Service Management Windows service is not created.


  • As a result, the Jazz for Service Management server does not automatically start when you restart the computer or log off of your Windows session. Tivoli Storage Productivity Center reports cannot connect to Jazz for Service Management. You must manually start Jazz for Service Management server every time you restart the computer or log off of your Windows session on which Jazz for Service Management is installed.

    To start the Jazz for Service Management server, run the following command:

    JazzSM_install_directory\profile\bin\startServer.bat server_name

    JazzSM_install_directory and server_name were specified when you installed Jazz for Service Management. The default JazzSM_install_directory is C:\Program Files\IBM\JazzSM, and the default server_name is server1.

    It might take a few minutes for the server to start.

    You can also return the name and status of the server by entering the following WebSphere® Application Server command:

    serverStatus -All
  • Jazz for Service Management launchpad uses the same default ports as IBM® Tivoli Integrated Portal Version 1.1, which can create a port conflict when you upgrade to Version 5.2.1 or later.
    When you upgrade from Tivoli Storage Productivity Center Version 4.2 (or later) to Tivoli Storage Productivity Center Version 5.2.1 (or later), there is a port conflict, the Jazz for Service Management launchpad does not provide an option to use non-default ports. The Jazz for Service Management launchpad also does not detect the port conflict if the Tivoli Integrated Portal Version 1.1 server is down.
  • If you try to install Jazz for Service Management separately by using a Windows domain user account, the installation will fail.


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.3 Knowledge Center and the 5.2.3 Installation Guide on page 187.

Tip for scheduling probes

When scheduling probes to collect data about resources, schedule the probes to run at different times. By scheduling data collection so that no two probes run at the same time, you can help improve the overall performance of the product and ensure that data is collected successfully. Probes are scheduled when you add resources for monitoring, and you can modify schedules at a later time. To modify the schedule for an existing probe, complete the following steps:
  1. Access the web-based GUI.
  2. From the navigation pane, go to the resource list page for a resource type. For example, to modify a probe schedule for a storage system, click Storage Resources > Storage Systems.
  3. Right-click the resource that you want to modify and select Data Collection > Schedule.
  4. On the Data Collection Schedule window, modify the schedule for the probe and click Save.

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.

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".

Installing on a Windows domain - documentation corrections

Topic title: Installing Tivoli Storage Productivity Center on a Windows domain

This Knowledge Center topic requires changes to step 2 in two sections.

Section title: Installing DB2 and Tivoli Storage Productivity Center by using local user accounts

Updated step 2 in this section:
    2. Log on to the Windows domain computer on which you plan to install Tivoli Storage Productivity Center by using a local user account that is a member of the local administrator and the local DB2 administrator (DB2ADMNS) groups.

Section title: Installing DB2 by using a local user account and Tivoli Storage Productivity Center by using a domain user account

Updated step 2:
    2. Log on to the Windows domain computer on which you plan to install Tivoli Storage Productivity Center by using a domain user account that is a member of the local administrator and the local DB2 administrator (DB2ADMNS) groups.
    This user must have the 'Act as part of the operating system' and 'Login as a
    service' permissions set in the security policy.

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 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.

    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.

    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.

    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.

    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.

    Jazz for Service Management directories remain after you uninstall Tivoli Common Reporting

    After you uninstall Tivoli Common Reporting, the follow directories might still remain in 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.

      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.


      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.

      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.


      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 V5.1.1.2 to 5.2.1 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.1, 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.21. 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.1.

      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 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.


      When reconfiguring a running monitoring agent, the agent cannot be restarted to use the new configuration

      The Tivoli Storage Productivity Center Monitoring Agent can be used by the Tivoli Enterprise Monitoring Server to monitor systems in your enterprise. This monitoring agent is an optional program that you can install and use in your enterprise. You can reconfigure a monitoring agent, if necessary, by using the Tivoli Enterprise Monitoring Services Console. If the monitoring agent is running when you reconfigure an agent, the agent must be restarted for the new configuration to take effect. If the agent is running, you are asked if you want to restart it. However, the restart operation fails. If errors are returned that indicate the agent was not stopped and started, use the Tivoli Enterprise Monitoring Services Console to manually stop and then start the monitoring agent.

      Tivoli Storage Productivity Center cannot recognize SAN Volume Controller entities that return online

      Due to limitations in the native API of the Storwize family of devices, Tivoli Storage Productivity Center cannot recognize when SAN Volume Controller entities, such as vdisks, mdisks, mdiskgroups return online after being offline.  

      Tivoli Storage Productivity Center is informed when entities fail or go offline.

      On AIX operating systems, if the language is set to FR_FR, text might not appear correctly on some installation pages

      On AIX operating systems, if the language is set to FR_FR, the Welcome page and the Single Server Installation Information page may not display correctly. For example, text might be truncated or there might not be enough space between sentences.

      Default Scan alert not showing any resource bound to it

      If a scan targets multiple resources and fails on one or more of those resources, the Resource column will be blank or will display only one of the failing resources. To see status for all the resource targets for the scan, use the stand-alone GUI. In the navigation tree, click Tivoli Storage Productivity Center > Monitoring > Scans > TPCUser.Default Scan to view the scan definition panel and click View Job History to see the Job Management page.

      Tivoli Storage Productivity Center data is not displayed on IBM Tivoli Monitoring: Tivoli Enterprise Portal desktop client in a distributed configuration

      In some cases, the workspaces of the IBM Tivoli Monitoring Agent for Tivoli Storage Productivity Center do not display in the Tivoli Enterprise Portal (TEP) desktop client when the Tivoli Monitoring Agent is installed on the same server as the Tivoli Enterprise Monitoring Services, and the Tivoli Enterprise Portal server is installed on a different server. To resolve this, install the TEP user interface extension from the Tivoli Monitoring Agent package on the same machine that the TEP server is installed on.

      Tivoli Storage Productivity Center uninstallation hangs during DB2 uninstallation

      The Tivoli Storage Productivity Center uninstaller might hang while you are removing the database repository. This problem occurs in Windows environments. The DB2 service does not stop in a timely manner. As a result, the uninstallation hangs while you are waiting for the DB2 service to stop.



      To resolve this issue:
      1. On the Windows server, go to Control Panel > Administrative Tools.
      2. Open Services.
      3. Right-click the DB2 service (for example, DB2 - DB2COPY1 - DB20), and select Properties.
      4. In the General tab, use the Path to executable value to identify the location of the DB2 executable file: db2syscs.exe. Close Services.
      5. Start the Windows Task Manager.
      6. In the Processes tab, select the db2syscs.exe file.
      7. Click End Process. The DB2 service stops, and the Tivoli Storage Productivity Center uninstallation continues.
      8. When the uninstallation is complete, restart the Windows server.

      Note: Windows hotfix KB2523134 resolved this problem.

      New DB2 installation might fail if the DB2 service user ID does not exist
      When you install DB2 9.7 fp9 in a Windows environment, the DB2 installation might fail if the DB2 service user ID does not exist. Check the DB2 installation log. The default location of the DB2 installation log file is My Documents\DB2LOG\ directory, and uses the following format: DB2-ProductAbrrev-DateTime.log. For example, DB2-ESE-Tue Apr 04 17_04_45 2008.log. This applies to new DB2 installations, not upgrades of existing DB2 installations.

      If the DB2 service user ID does not exist, the DB2 installation log file contains one of the following error messages:
      • ERROR: One or more errors occurred while creating the DB2 Administration Server. The DB2 Administration Server might not function properly. To resolve this, create the DB2 Administration Server manually. If the problem persists contact your technical service representative.
      • An error occurred while running the command "C:\Program Files\IBM\SQLLIB\bin\db2.exe\CREATE TOOLS CATALOG SYSTOOLS USE EXISTING DATABASE TOOLSDB FORCE" to initialize or upgrade the DB2 tools catalog database. The return value is "4".

      To resolve the issue, create the default db2admin user ID manually before you install
      DB2, or upgrade from an earlier version of DB2. For example, upgrade from DB2 9.7 fp8.

      Internet Explorer v10 hangs when you use the transform plan or analysis execution panes after you view logs

      Internet Explorer v10 hangs and must be closed when you use the transform plan or analysis execution panes after you open and close log files. To resolve the problem, close and restart Internet Explorer. To avoid the problem, use a different web browser.

      Data displayed in other Tivoli products uses older data type labels

      When Tivoli Storage Productivity Center data is displayed in other Tivoli products, such as Tivoli Business Service Manager and Tivoli Application Dependency Discovery Manager, those applications use incorrect labels for some data types. The incorrect labels are from Tivoli Storage Productivity Center version earlier than V5.2.

      Other Tivoli applications might also use GB or MB capacity values rather than GiB or MiB, which Tivoli Storage Productivity Center V5.2 and later use.

      Examples:
      Pre-TPC5.2.x LabelTPC 5.2.x Label
      Volume Group CapacityPool Capacity
      Volume Group Freespace Available Pool Space
      Allocated CapacityAssigned Volume Space
      Available CapacityUnassigned Volume space


      Installation fails on Windows 2008 R2 in Russian language

      The Tivoli Storage Productivity Center installation fails on Windows 2008 R2 on a Russian language server. This is caused by a known DB2 issue.

      Total Capacity statistic in Tivoli Common Reporting reports is incorrect in some cases

      If a group includes a volume that is configured as back-end storage for a storage virtualizer, the Total Capacity value for that group that is displayed Tivoli Common Reporting reports might not be correct.

      Linux file system capacity is reported differently by Tivoli Storage Productivity Center and TADDM

      The capacity of Linux file systems is reported differently by Tivoli Storage Productivity Center and Tivoli Application Dependency Discovery Manager. The capacity value reported by Tivoli Storage Productivity Center is generally very similar to the value reported by the Linux operating system.

      Tivoli Common Reporting tasks might fail if not configured to use the correct DB2 instance on AIX and Linux

      If you install more than one instance of DB2, you must ensure that either:
      • the Tivoli Common Reporting TPCDB data source uses the default DB2 instance, or
      • the TPCDB database is cataloged in the default DB2 instance.

      Otherwise, Tivoli Common Reporting tasks might fail.

      Upgrade from V5.x to V5.2.2 fails if a Replication CLI session is running

      If you have a Replication CLI session running in a console window on your server and you attempt to upgrade from Tivoli Storage Productivity Center V5.x to V5.2.2, the upgrade will fail during the Websphere Application Server portion of the upgrade. You will see error message BPCIN0004E because the CLI session locks certain files and does not allow those files to be overwritten during the upgrade.

      To prevent this situation, make sure all CLI windows are closed before upgrading to Tivoli Storage Productivity Center V5.2.2.


      When installing V5.2.3 Storage Resource agents using the local CLI, you must replace the existing server SSL certificates

      A new installation of Tivoli Storage Productivity Center V5.2.2 and V5.2.3 uses SSL certificates with a 2048-bit key. However, if the server was upgraded from an earlier version to V5.2.2 or V5.2.3, then the server still uses certificates with a 1024-bit key. If you install V5.2.2 or V5.2.3 Storage Resource agents using the command line installation procedure from the installation image, and point those agents to an upgraded server, the agent installation will fail due to a certificate mismatch. To install V5.2.2 or V5.2.3 Storage Resource agents using the local command line, the 2048-bit certificates in the install image on the agent system must be replaced with 1024-bit certificates using the following steps.

      Restriction: This process assumes that the Storage Resource agent disk image can be modified. If you are installing from a DVD, you must copy the installation files to a location where you have write access before you implement the following steps.

      1. Copy <TPC_installation_directory>/data/sra/<agent_operating_system>/certs.zip from the upgraded Tivoli Storage Productivity Center server to <SRA_image_install_directory>/sra/<agent_operating_system> on the agent system.

      2. Extract the zip file to <SRA_image_install_directory>/sra/<agent_operating_system>/certs.

      Note: <SRA_image_install_directory> is the directory where the Storage Resource agent image was extracted. <agent_operating_system> is the directory that is named for the operating system where the agent is installed.

      3. Install the Storage Resource agent with the appropriate option.

      APAR 99467: Updated online help topic: Triggering conditions for storage system alerts

      The table in this topic has been updated to include a notation that the Node Status Change Offline and Node Status Change Online triggering conditions do not generate alerts for Storwize devices and SAN Volume Controller.

      This topic will also be updated in the Tivoli Storage Productivity Center V5.2.3 Knowledge Center.

      APAR IC98638: Information Center incorrectly references the Configuration Utility

      In the IBM Tivoli Storage Productivity Center V5.2 and 5.2.1, the Configuration Utility and Configure Devices functions were moved from the stand-alone GUI to the web-based GUI. You can view a list of functions that were moved to the web-based GUI here:
      http://www.ibm.com/support/knowledgecenter/SSNE44_5.2.1/com.ibm.tpc_V521.doc/tpch_r_ui_changes_v52.html

      The following functions are no longer available in the stand-alone GUI:

      Viewing reports and topology for the XIV system environment
      To view the Tivoli Storage Productivity Center reports and topology for the XIV system environment, complete the following steps:
        1. Start the web-based GUI.
        2. In the navigation pane, select Storage Resources > Storage Systems.
        3. Click Add Storage System.
        4. Click the XIV icon.
        5. In the Add Storage System wizard, add the storage system that you want to monitor.
        6. After you add the XIV system, an automatic discovery and probe are started.
        7. View the reports and topology for the XIV system in Tivoli Storage Productivity Center.

      Error message GUI8293E is no longer valid
      Error message GUI8293E is no longer valid and will be removed in a future release. Disregard any references to the Configuration Utility.

      User account is locked after the DS Storage manager password for the DS8000 HMC is
      changed
      To resolve this, follow these steps to update the password for the element manager. If the passwords for multiple element manager users have changed, you must update the password for each user.
        1. Start the Tivoli Storage Productivity Center web-based GUI.
        2. In the navigation pane, select Storage Resources > Storage Systems.
        3. Right-click the DS8000 and select Open Storage System GUI.
        4. Log in to the IBM System Storage DS8000 Sign On panel and update the user password. Follow the instructions provided in the DS8000 Information Center:
      http://publib.boulder.ibm.com/infocenter/dsichelp/ds8000ic/index.jsp?topic=%2Fcom.ibm.storage.ssic.help.doc%2Ff2c_polcybasicusrmodfy_070511a.html

      APAR IC99222: Stop all jobs and reboot servers before upgrading Tivoli Storage Productivity Center

      Follow these steps before upgrading Tivoli Storage Productivity Center:

      1. Stop all jobs including performance monitor jobs, system and fabric probe jobs, scan jobs, and other probe jobs.

      2. If possible, reboot the Tivoli Storage Productivity Center servers. This will stop any remaining Tivoli Storage Productivity Center Java processes that might not stop in a timely manner. If a reboot is not possible, stop and restart the Tivoli Storage Productivity Center server service. It is important that the Tivoli Storage Productivity Center Device server stops and restarts cleanly. If this does not occur, a server reboot might be required.

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


      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:

      Virtual Machine Disks (VMDKs) in a data store that is mounted on multiple hypervisors might be displayed incorrectly under one hypervisor

      Although the VMDKs are in a data store that is mounted on multiple hypervisors, if they are not assigned to a disk they are listed under one hypervisor. For example, the VMDKs are for a disk that was deleted.

      If one of the hypervisors where the data store is mounted is not probed, the VMDKs in the data store that are assigned to disks for virtual machines that belong to that hypervisor are listed by the other hypervisors.

      Following redeployment, the Tivoli Storage Productivity Center build version does not match the version number of the vSphere Web Client extension

      After you redeploy the vSphere Web Client extension, the Tivoli Storage Productivity Center build version might not match the version number of the vSphere Web Client extension. To resolve this issue, complete the following steps to redeploy the extension:

      1. On the vSphere Web Client computer that connects to the vCenter Server system where the extension is installed, go to the plug-in directory:
      • On Windows operating systems:
        • C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-clientserenity
      • On Linux operating systems:
        • /var/lib/vmware/vsphere-client/vc-packages\vsphere-client-serenity

      2. Delete the packages for the vSphere Web Client extension. Package files use the following naming convention: com.ibm.tpc-TPC-build-number.

      3. Delete the TPCServerConfiguration.properties file. The file is stored in the following location:
      • On Windows operating systems:
          %PROGRAMDATA%\IBM\TPC

          For example, C:\ProgramData\IBM\TPC\ or %ALLUSERSPROFILE%\IBM\TPC
          For example, C:\Documents and Settings\All Users\IBM\TPC\
      • On Linux operating systems:
          /opt/IBM/TPC

      4. Redeploy the vSphere Web Client extension.

      5. Restart the VMware vSphere Web Client service.

      6. Log in to the vSphere Web Client. From the vSphere Web Client Home tab, in the Administration section, click the IBM Tivoli Storage Productivity Center icon. Confirm that the Tivoli Storage Productivity Center build version matches the version number of the vSphere Web Client extension.

      Disable Windows User Access Control to edit configuration files

      On Windows installations, if you installed Tivoli Storage Productivity Center by using a domain user account, you must disable User Account Control to edit the vasa_filter.properties file.

      Provisioning with VMware datastore creation to a clustered ESX 5.1 is partially complete
      If you provision storage with datastore creation to two clustered ESX 5.1 hypervisors by using the vSphere Web Client extension, the datastore is not assigned to the second hypervisor. The datastore is not assigned because of a LUN snapshot issue in VMware vCenter Server.

      To learn how to resolve this issue, go to the VMware Knowledge Base at http://kb.vmware.com/selfservice. Search for vSphere handling of LUNs detected as snapshot LUNs (1011387).

      vCenter 5.1 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 5.1 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.

      Upgrade to vCenter 5.5 Server to resolve this issue.

      Storage DRS calls fail for datastore clusters with file system storage

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

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

      In a datastore clustered NFS environment, vCenter 5.1 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. Upgrade to vCenter 5.5 Server to resolve this issue.

      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 5.1 Server from the Tivoli Storage Productivity Center VASA provider might be displayed in the Events panel, instead of the Alarms panel. Upgrade to vCenter 5.5 Server to resolve this issue.

      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 5.1 Server. If the LUN belongs to a datastore, two non-relevant events are displayed. Upgrade to vCenter 5.5 Server to resolve this issue.

      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 5.1 Server, an unknown vCenter identifier is displayed. Upgrade to vCenter 5.5 Server to resolve this issue.

      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. Upgrade to vCenter 5.5 Server to resolve this issue.

      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. Upgrade to vCenter 5.5 Server to resolve this issue.

      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 work around, 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 time-out. The default for this time-out is 120 minutes.

      If a time-out 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.

      Deploying the vSphere Web Client extension on vCenter Server 5.5 fails on Windows 2008 or Linux

      If you deploy the vSphere Web Client extension from a Tivoli Storage Productivity Center server onto a vCenter Server 5.5 that is installed on Windows 2008 or Linux, the deployment fails. The following message is displayed:
      BTAVM2244E The remote registration of the vSphere Web Client extension for Tivoli Storage Productivity Center did not complete.

      The deployment fails due to a handshake issue with the vSphere Client, vSphere PowerCLI, and vCenter Server 5.5.

      To learn how to resolve this issue, go to the VMware Knowledge Base at
      http://kb.vmware.com/selfservice. Search for vSphere Client and vSphere PowerCLI
      may fail to connect to vCenter Server 5.5 due to a Handshake failure (2049143).

      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:

      [{"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.2.3","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}},{"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":null,"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.2.1","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

      Document Information

      Modified date:
      22 February 2022

      UID

      swg21677022