IBM Support

5.2.7.x 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 V5.2.7.x or Tivoli® Storage Productivity Center for Replication V5.2.7.x

Content


This document contains the following sections:


Support links and documentation

Installation, upgrade, and configuration

General Tivoli Storage Productivity Center issues

Language-related issues

Other monitoring products

Tivoli Common Reporting

Tivoli Storage Productivity Center for Replication

Documentation updates and corrections

Microsoft Internet Explorer

VMware vSphere



Support links and documentation
To access all of the support documentation for Tivoli Storage Productivity Center and IBM Spectrum Control, including alerts and APARs, go to the IBM Support Portal.

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 V5.2.7 Quick Installation Guide and other publications, see the printable documentation download web site at ftp://public.dhe.ibm.com/software/tivoli/tpc/v527/.

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

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 .


Product licenses for Tivoli Storage Productivity Center

Tivoli Storage Productivity Center V5.2.7 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.7/com.ibm.tpc_V527.doc/fqz0_t_upgrading_im.html.


Option to install or upgrade reporting components might not be available when you upgrade from Tivoli Storage Productivity Center V 5.2.x to V5.2.y

The instructions for upgrading Tivoli Storage Productivity Center that are in the product documentation include steps for installing or upgrading Jazz for Service Management and Tivoli Common Reporting and Tivoli Storage Productivity Center reports during the upgrade process. However, the option to install or upgrade these reporting components when you upgrade Tivoli Storage Productivity Center V5.2.x to V5.2.y might not be available. The ability to install or upgrade reporting components during the 5.2.x to 5.2.y upgrade process depends on the status of your reporting environment before the upgrade as described in the technote at http://www.ibm.com/support/docview.wss?uid=swg21687650.


Installation, upgrade, and configuration



SSLv3 disabled by default

Before you upgrade to Tivoli Storage Productivity Center V5.2.5 or later, read and understand the information in this security bulletin: Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect Tivoli Storage Productivity Center October 2014 CPU.

SSLv3 (the legacy SSL protocol) has been disabled by default once you upgrade to Tivoli Storage Productivity Center 5.2.5 and later releases. To maintain compatibility between Tivoli Storage Productivity Center and storage systems or devices that support only SSLv3, you must upgrade the storage systems and devices to a level that provides TLS support (if available) or manually enable SSLv3 in Tivoli Storage Productivity Center using a script after you upgrade. Information about using the script to enable SSLv3 is provided in the link in the security bulletin.

The Supported Hardware, Products and Platforms Interoperability Matrix Links support pages have been updated to reflect known compatibility considerations related to this security update.

Related Information: Security Bulletin: Multiple vulnerabilities impact DS8000 HMC.

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.

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.

During upgrade from Tivoli Storage Productivity Center 4.2.2.8 or 4.2.2.9, systems with fabric CIMOMs may encounter GUI8224E Internal Error message

To work around this issue, remove any fabric CIMOM added at the 4.2.2.8 or 9 level and restart the upgrade.

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.

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.


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.

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

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.

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

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

Replacing existing server SSL certificates when upgrading from versions earlier than V5.2.2

Tivoli Storage Productivity Center Version 5.2.2 (or later) uses SSL certificates with 2048-bit encryption keys whereas previous versions of Tivoli Storage Productivity Center used 1024-bit encryption keys. If you upgrade Tivoli Storage Productivity Center from a version earlier than V5.2.2, your SSL certificates are not updated automatically to 2048-bit encryptions keys. If you want to use 2048-bit encryption keys with previous versions of Tivoli Storage Productivity Center, you must replace the default SSL certificates with custom SSL certificates.

For information about how to replace SSL certificates, see Replacing custom SSL certificates in the IBM Knowledge Center: https://www.ibm.com/support/knowledgecenter/SSNE44_5.2.7/com.ibm.tpc_V526.doc/fqz0_r_create_custom_certificate_ssl.html

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 or later uses SSL certificates with a 2048-bit key. However, if the server was upgraded from an earlier version to V5.2.2 or later, then the server still uses certificates with a 1024-bit key. If you install V5.2.2 or later 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 later 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.


Changing the synchronization rate for volumes on SAN Volume Controller or Storwize family systems 
The synchronization rate on SAN Volume Controller is the rate at which the volume copies synchronize again after synchronization is lost. 

Tivoli Storage Productivity Center can do tasks that significantly alter the structure of storage. For example, Tivoli Storage Productivity Center can add a mirrored volume copy, or migrate volumes from one pool to another by using the storage optimizer functions. When Tivoli Storage Productivity Center does these tasks, by default, the synchronization rate is set to 100%. 

The synchronization rate can cause performance problems on all SAN Volume Controller volumes. However, you can use the tpctool command to change the synchronization rate. 

For more information about how to change the synchronization rate, go to the "Changing the synchronization rate for volumes on SAN Volume Controller or Storwize family systems" technote at  http://www.ibm.com/support/docview.wss?uid=swg21972452. You can track the status of the associated APAR here: http://www.ibm.com/support/docview.wss?uid=swg1IT11274.


General Tivoli Storage Productivity Center issues



Cannot acknowledge the health status of secondary volume copies

IBM Spectrum Control checks the status of a resource during data collection. If the status of a resource is Warning, Error, or Unreachable, you can mark that status as acknowledged. For mirrored volumes in storage systems that run IBM Spectrum Virtualize, you cannot acknowledge the health status of secondary volume copies if both of the following conditions are true:
  • The status of the primary volume copy is Online.
  • The status of the secondary volume copy is Offline, Error, or Warning.


Renewing security certificates

When you receive notifications that your Tivoli Storage Productivity Center security certificates are expiring or have expired, you can renew them using the procedure described in this IBM Knowledge Center topic:

Renewing security certificates

http://www.ibm.com/support/knowledgecenter/SS5R93_5.2.9/com.ibm.spectrum.sc.doc/fqz0_t_tbs_renewing_security_certificates.html

This topic is part of the IBM Spectrum Control V5.2.9 Knowledge Center, but applies to Tivoli Storage Productivity Centerl V5.2.7 as well. This topic also resolves APAR IT11179.


Information about resources that use the iSCSI protocol is not shown in Tivoli Storage Productivity Center

Tivoli Storage Productivity Center does not collect iSCSI port information for storage systems and servers. Information about resources that connect to monitored storage systems using the iSCSI protocol is not shown in the web-based GUI. For example, information about iSCSI mapped volumes is not shown.

Provisioning fails with ADD_PORTS_TO_HOST message on XIV 11.5.0 when modifying host

When trying to provision storage from an XIV 11.5.0 system, the provisioning task fails with an "ADD_PORTS_TO_HOST task failed" message when trying to provision storage to a host that is already defined on the XIV subsystem. This can happen when the host definition does not contain all the Fibre Channel ports that Tivoli Storage Productivity Center is trying to assign the volume to.

For example, if you try to provision storage to a host that has 2 Fibre Channel ports and the host is
already defined on the XIV 11.5.0 system but with only one of the Fibre Channel ports, the assign job will fail and the second port will not be added to the host.

This condition does not occur when Tivoli Storage Productivity Center is creating the host definition, or when an existing host definition already has all ports defined. This issue does not occur with XIV 11.4 systems, and 11.5.1 or later systems.

Workaround: modify the host definition on the XIV 11.5.0 system to contain all the Fibre Channel ports, then run a probe of the XIV 11.5.0 system in Tivoli Storage Productivity Center or upgrade to XIV 11.5.1 or later.

Displaying the web-based GUI in high contrast mode

You might encounter minor display 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.

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.

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.
The stand-alone GUI reports N/A for some XIV system values
  • When you generate a Constraint Violation report for an XIV system in the stand-alone GUI Disk Manager>Reporting>Storage Subsystem Performance>Constraint Violation report, the Measured Value is reported as N/A for theTotal Port I/O Rate threshold.
  • When you generate a performance report for an XIV system, such as Disk Manager>Reporting>Storage Subsystem Performance>by Storage Subsystem, N/A values are reported for Total Port I/O Rate and Total Port Data Rate.
  • To obtain valid values for Total Port I/O Rate and Total Port Data Rate, run the Disk Manager>Reporting>Storage Subsystem Performance>by Port report.

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.

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.

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.

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


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.

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.

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.

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:

Language-related issues

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.

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.

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.

Other monitoring products

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

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 similar to the value reported by the Linux operating system.

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 Label TPC 5.2.x Label
Volume Group Capacity Pool Capacity
Volume Group Freespace Available Pool Space
Allocated Capacity Assigned Volume Space
Available Capacity Unassigned Volume space

Tivoli Common Reporting



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.

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.

Cognos BI reports display incorrect data for some performance metrics

Cognos BI reports display incorrect data for the following performance metrics:
  • The performance metric "Overall Write Cache Hit Percentage" displays incorrect data for SAN Volume Controller, Storwize, and FlashSystem storage systems. The displayed value is 100 times the actual value, so a write cache hit percentage displayed as 1234% is actually 12.34%. However, the same metric displays the correct value in the web-based GUI and in the stand-alone GUI.
  • The performance metric "Dirty Write Percentage of Cache Hits" displays incorrect data for SAN Volume Controller, Storwize, and FlashSystem storage systems with firmware version 7.3 or later. The displayed value is -1.00% but should display as a blank. This metric is deprecated for firmware version 7.3 or later. However, the same metric displays the correct value in the web-based GUI and the stand-alone GUI.

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.


Tivoli Storage Productivity Center for Replication



Communication error issue with DS8000

IBM® Tivoli® Storage Productivity Center for Replication may experience a connection issue with the secondary DS8000 HMC. If the connection between TPC-R's ESSNI client and one HMC fails, then the ESSNI client may not switch to the secondary HMC but return an error. A fix is available as a patch, contact IBM Support to request the fix for APAR IT18791. For additional information, see APAR IT18791


Error occurs when logging into Tivoli Storage Productivity Center for Replication for System z

During the login procedure to the IBM® Tivoli® Storage Productivity Center for Replication for System z® GUI, the message "IWNR4006E The user name and/or password is invalid" can occur, even though you are attempting to log in with the correct user name and password. This can happen when running Tivoli Storage Productivity Center for Replication for System z with program control enabled in the UNIX System Services.

For instructions about how to resolve this issue, see this technote: http://www.ibm.com/support/docview.wss?uid=swg21974311.

Documentation update: DS8000 storage system default ports

In table 2 of the 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.7>Product overview>Key concepts> Ports.


HyperSwap commands might unfence the alternate target device of a multi -target session type

Under some conditions when using the multi-target session type, HyperSwap commands might unfence the alternate target device , This can counteract the resiliency improvements in DS8870 for zOS HyperSwap Soft Fence, which prevents a host from reading or writing data on the previous primary storage system after a HyperSwap occurs. If the alternate target device is unfenced, it might access data from the previous primary PPRC site when an unplanned recovery occurs in your storage environment. To prevent this condition, make sure you know which volume you are using to IPL.


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.


Documentation updates and corrections



The documentation incorrectly states that SNMP version 3 is supported in Tivoli Storage Productivity Center V5.2.7

Several topics in the IBM Knowledge Center and other V5.2.7 publications incorrectly state that SNMPv3 is supported in this release. SNMPv3 will be supported in a future release, but is not supported in the V5.2.7 release.

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

Incorrect file name for database maintenance tool

In the following topics, the name of the database maintenance tool for Linux and UNIX operating systems is incorrect: The correct name of the database maintenance tool is runTPCDBMaintenance. That is, the file does not have a .sh extension. This correction also applies to the Knowledge Centers for the following releases of Tivoli Storage Productivity Center: 5.2.6, 5.2.5, 5.2.4, 5.2.3, 5.2.2.

Microsoft Internet Explorer issues



Internet Explorer version 11 displays a security certificate error

If you use Internet Explorer version 11 to run the web-based GUI, you might see this error page appear in all open Internet Explorer windows and tabs: "There is a problem with this website's security certificate." To return to the web-based GUI page you were working on, click "Continue to this website" and you will be returned to the previous page. This behavior does not occur in other browsers.

Alerts Notification Settings display as available in Internet Explorer version 11

When viewing the Alerts Notification Settings page by using Internet Explorer version 11, some check boxes might appear as available (selectable) when they should be disabled. To change the Alerts Notification Settings, click Edit on the Alerts Notification Settings page.

This condition does not occur in other browsers.


Tables automatically scroll in Internet Explorer version 11

When using Internet Explorer version 11 to work with Tivoli Storage Productivity Center, selecting a row in a table might cause the web page to scroll automatically to a point where the first row of the table is at the top of the page. This behavior does not occur in other browsers.


Online help table of contents does not display properly in Internet Explorer 11

The table of contents for the Tivoli Storage Productivity Center online help does not display correctly in Microsoft Internet Explorer version 11. All sections are automatically expanded, and cannot be collapsed. This behavior does not occur in other recommended browsers.


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.

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:

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.

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.

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


Limitations when using vCenter 5.1
The following are limitations when using vCenter 5.1. They are resolved in vCenter 5.5.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

Document information

More support for: Tivoli Storage Productivity Center

Software version: 5.2.7

Operating system(s): AIX, Linux, Windows

Software edition: All Editions

Reference #: 1960887

Modified date: 12 November 2017