Tivoli Storage Productivity Center: Flash for Version 4.1.1

Preventive Service Planning


Abstract

This Flash contains last-minute information and changes that could not be included in the final product documentation for Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication. This document also contains information about known issues.

Content

1.0 IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication: Flash for Version 4.1.1


    1.1 Important notice about the WebSphere Application Server
    1.2 Important notice about installation
    1.3 Important notice creating SAN Volume Controller VDisks
    1.4 Important notice about performance monitoring of DS8000 storage systems
    1.5 Important notice about Tivoli Storage Productivity Center for Replication in a VMware image
    1.6 Fix packs
    1.6.1 New in version 4.1.1 fix pack 1 (December 2009)
    1.6.2 New in version 4.1.1 fix pack 2 (March 2010)
    1.6.3 New in version 4.1.1 fix pack 3 (May 2010)
    1.6.4 New in version 4.1.1 fix pack 4 (August 2010)
    1.6.5 New in version 4.1.1 fix pack 5 (October 2010)
    1.6.6 New in version 4.1.1 fix pack 6 (April 2011)
    1.6.7 New in version 4.1.1 fix pack 7 (February 2012)
    1.7 New in version 4.1.1
    1.8 Installing, upgrading, or migrating to Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication Version 4.1.1
    1.9 Using Tivoli Storage Productivity Center
    1.10 Known limitations
    1.11 Known issues
    1.12 Documentation corrections

    *** Note: Recent changes to this flash are indicated by asterisks (***).

    1.0 IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication Flash for Version 4.1.1

    In addition to this document, you should read the following documents before using this product:
    • IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication Installation and Configuration Guide
    • IBM Tivoli Storage Productivity Center User's Guide

    Access the IBM Tivoli Storage Productivity Center Information Center here:

    http://www-01.ibm.com/support/knowledgecenter/SSNE44_4.1.0/com.ibm.tpc_V41.doc/welcome.html

    This site contains the most recent versions of the publications in PDF and HTML formats, or both. Translated documents are also available for some products.

    You must have the Adobe Acrobat Reader in order to view the PDF format of the publications. You can download the Adobe Acrobat Reader from:

    http://www.adobe.com/products/acrobat/readstep2.html

    1.1 Important notice about the WebSphere Application Server

    Customers who have Web based applications, including Web services applications running on WebSphere Application Server, have a risk for an attacker to have the ability to remotely display or execute files on the server contained within a within a war file, including files under the web-inf and meta-inf directories. In addition, there is a potential risk for customers who are using the WebSphere administrative console with administrative security disabled.

    WebSphere Application Server has updates available for APAR PK81387. The interim fix needs to be applied to the following WebSphere Application Servers for Tivoli Storage Productivity Center version 4.1.1 in the table below.

    Note: This does not apply to the Tivoli Storage Productivity Center Device Server, which is at version 6.1.0.23. Also, this does not apply to the WebSphere Application Server on z/OS.

    Installed version Location
    Tivoli Integrated Portal 6.1.0.21 <IBM_install_directory>\tivoli\tip\
    Agent Manager 6.1.0.5 <IBM_install_directory>\
    <Agent_Manager_directory>

    The default installation directory is C:\Program Files\IBM\TPC for Windows and /opt/IBM/TPC for UNIX and Linux.


    1.2 Important notice about installation
    • When installing the Tivoli Storage Productivity Center family, both the Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication components will be installed. Canceling installation at any time during the install process will result in the uninstall of all components. For example, clicking the Cancel button during the installation of the Tivoli Storage Productivity Center for Replication component will result in the uninstallation of Tivoli Storage Productivity Center, Tivoli Integrated Portal, and Tivoli Storage Productivity Center for Replication components.
    • The Tivoli Storage Productivity Center server requires a static IP address.
    • When you install a new version of Tivoli Storage Productivity Center for Replication, DB2 is not used as the database. When you upgrade Tivoli Storage Productivity Center for Replication from a previous release to version 4.1 or later, and have DB2 as the database, DB2 is upgraded for Tivoli Storage Productivity Center for Replication. If you have the situation where DB2 is used as the database for Tivoli Storage Productivity Center for Replication, WebSphere Application Security must be turned off before you upgrade.
      Note: This does not apply to z/OS.
    • Tivoli Storage Productivity Center 4.1.1 installation fails when creating the database schema using DB2 9.1 with Fix Pack 5 on Windows 64-bit machine with more than 4 GB of memory. See DB2 APAR:
      http://www-01.ibm.com/support/docview.wss?uid=swg1JR30491

      To resolve this issue, use DB2 9.5 with Fix Pack 4.

    1.3 Important notice about SAN Volume Controller VDisks

    When creating SAN Volume Controller VDisks with Tivoli Storage Productivity Center, there could be a potential issue in some cases where the SVC cache function is disabled for the VDisk. This situation can lead to performance problems for applications using the VDisks.

    For more information about this issue, see fqz0_r_svc_cache.pdf below.

    1.4 Important notice about performance monitoring of DS8000 storage subsystems

    When using Tivoli Storage Productivity Center 4.1.1 to run performance monitors for DS8000 storage subsystems with a microcode version between 5.4.2.1 and 5.4.3.51, the performance monitors might fail to collect performance statistics from the storage subsystems. Tivoli Storage Productivity Center contains new features to take advantage of recent additions to the set of DS8000 performance metrics supported by the subsystems. However, these earlier microcode releases might cause the Tivoli Storage Productivity Center 4.1.1 performance monitors to fail. If the performance monitoring function is required for DS8000 storage subsystems in your environment, you should upgrade to DS8000 microcode version 5.4.3.52 (bundle 64.30.78.0) or higher before upgrading to Tivoli Storage Productivity Center 4.1.1.55. If you cannot upgrade your DS8000 at this time, you should apply the temporary fix or upgrade to 4.1.1 fix pack 1 when available. See this technical note for further information: http://www-01.ibm.com/support/docview.wss?&uid=swg21408590.

    1.5 Important notice about Tivoli Storage Productivity Center for Replication in a VMware image

    Tivoli Storage Productivity Center for Replication only supports VMware while under a Request for Price Quotation (RPQ). Tivoli Storage Productivity Center for Replication is a mission-critical application used to maintain a consistent copy of customer data. If you run this product under a VMware image, you should be aware of the following known issues:
    • Virtual machines can be moved from one physical server to another using VMotion or other tools. If you move your virtual machine with Tivoli Storage Productivity Center for Replication on it, unpredictable results can occur during certain critical operations. This action could prevent maintaining data consistency.
    • If the VMware image resides on the same storage managed by Tivoli Storage productivity Center for Replication, then Tivoli Storage Productivity Center for Replication might attempt to "freeze" I/O on the storage system, which would cause Tivoli Storage Productivity Center for Replication to stop responding. If this freeze occurs, the I/O will not be released until the storage system freeze time-out occurs. Any applications running against that storage system could experience a long period of application impact.

1.6 Fix packs
A summary of the fix packs and interim fixes provided is available from the Latest Downloads for Tivoli Storage Productivity Center support page at http://www-01.ibm.com/support/docview.wss?&uid=swg21320822.

*** 1.6.1 New in version 4.1.1 fix pack 1 (December 2009)

The IBM Tivoli Storage Productivity Center family 4.1.1 fix pack 1 adds the following functions:
  • Storage resource agents are now supported on SUSE Linux Enterprise Server 11.
  • Tivoli Storage Productivity Center volume provisioning support has been added for Hewlett Packard XP storage subsystems. Hewlett Packard CIM agent version 6.2 is supported. For more information, see http://www-01.ibm.com/support/docview.wss?uid=swg21406692.
  • Tivoli Storage Productivity Center supports performance management for Hitachi Data Systems storage subsystems with HDvM 6.1 and 6.2 SMI-S provider. For more information, see http://www-01.ibm.com/support/docview.wss?uid=swg21406692.
  • The Storage Optimizer is now supported for DS8700.

Tivoli Storage Productivity Center assumes that the DS8700 is a dual four-way processor complex for every storage subsystem it models. Tivoli Storage Productivity Center does not have information from the storage subsystem to detect if the subsystem has a dual four-way processor complex or dual two-way processor complex.

Upgrading a license for IBM® Tivoli® Storage Productivity Center for Replication for System z®

You can upgrade an existing two-site or three-site license for IBM® Tivoli® Storage Productivity Center for Replication for System z® by performing these steps:
  1. Install IBM Tivoli Storage Productivity Center for Replication for System z two-site or three-site license with SMP/E. See the IBM Tivoli Storage Productivity Center for Replication for System z Program Directory for detailed installation instructions.
  2. Run IWNINSTL with no errors.
  3. Start IBM Tivoli Storage Productivity Center for Replication.

Tivoli Storage Productivity Center now supports the LSI SMI-S Provider level 10.06.GG.33 or later for IBM System Storage DS4000 and IBM System Storage DS5000. The LSI SMI-S Provider supports the Storage Management Initiative Specification (SMI-S) 1.3 specifications. The LSI SMI-S Provider also provides performance metrics.

These are the issues with this support:
  • The performance monitor log shows frequent time out messages but does not collect any performance metric data. Work around: Restart the CIM agent.
  • The configuration operations fail even though all the settings are correct for a storage subsystem. Work around: Check the link status of the ethernet ports for the controllers of the subsystem using the DS Storage Manager. If the status shows "failed," then check the controller firmware. If the controller firmware version is less than 7.60.xx, then upgrade the firmware to level 7.60 or later.
  • Tivoli Storage Productivity Center supports up to five storage subsystems with the LSI SMI-S Provider 1.3.

*** 1.6.2 New in version 4.1.1 fix pack 2 (March 2010)

The IBM Tivoli Storage Productivity Center family 4.1.1 fix pack 2 adds the following support:
  • Cisco NX-OS 4.2
  • EMC SMI-S 4.1/Solutions Enabler 7.1.0.34 and EMC V-Max (limitations)
  • IBM XIV 2812-A14
  • VMware vSphere 4.0 (VMware virtualization software)

*** 1.6.3 New in version 4.1.1 fix pack 3 (May 2010)

Tivoli Storage Productivity Center for Disk Midrange Edition is now available (May 2010).

The IBM Tivoli Storage Productivity Center family 4.1.1 fix pack 3 adds the following support:
  • Hitachi Device Manager v6.3 support (see limitations for performance management)

Tivoli Storage Productivity center 4.1.1 fix pack 3 (4.1.1.84) was immediately replaced with 4.1.1 interim fix 1 (4.1.1.85) to address an installation issue fixed with APAR IC68457 affecting new installations with LDAP.

*** 1.6.4 New in version 4.1.1 fix pack 4 (August 2010)
The IBM Tivoli Storage Productivity Center family 4.1.1 fix pack 4 adds the following support:
  • DS8700 R5.1 Storage Optimizer Support
  • DS8700 R5.1 Support, including Storage Optimizer

*** 1.6.5 New in version 4.1.1 fix pack 5 (October 2010)
This fix pack provides APAR and defect fixes.

*** 1.6.6 New in version 4.1.1 fix pack 6 (April 2011)
This fix pack provides APAR and defect fixes.
*** IC76035 (53696)
Attempting to launch the Tivoli Storage Productivity Center GUI from the Tivoli Integrated Portal console fails because of an extra slash (/) character in the URL between ITSRM and app.

Example: http://your_IP:9550/ITSRM//app/tpcgui.jnlp

Work around: Use Java WebStart to launch the Tivoli Storage Productivity Center GUI:

https://your_IP:9550/ITSRM/app/en_US/index.html

or

Launch a new browser tab in the Tivoli Integrated Portal GUI and correct the URL by removing the extra slash:

http://your_IP:9550/ITSRM/app/tpcgui.jnlp

*** 1.6.7 Version 4.1.1 fix pack 7 (February 2012)

This fix pack provides APAR and defect fixes. It also applies updates to resolve the security alert for CVE-2010-4476 for the following components of Tivoli Storage Productivity Center:
  • Device Server
  • Data Server
  • Replication Server
  • Tivoli Integrated Portal
  • GUI Client
  • Agents
  • Storage Resource Agent
  • Common Agent

See the Tivoli Storage Productivity Center remediation technote for details on other components.


1.7 New in version 4.1.1 (4.1.1.55)

For more information about each of the features, go to the Tivoli Storage Productivity Center Information Center. For information about how to use the features, see the IBM Tivoli Storage Productivity Center User's Guide or IBM Tivoli Storage Productivity Center for Replication User's Guide.

IBM Tivoli Storage Productivity Center 4.1.1 adds the following new features, functions, and enhancements:

IBM System Storage DS8000 4.3

Tivoli Storage Productivity Center supports the DS8000 4.3 features described in this section.
    data encryption
    IBM Tivoli Storage Productivity Center supports storage subsystem data encryption for DS8000. To use data encryption, DS8000 uses full disk encryption drives. At this time, DS8000 does not support a mix of full disk encryption and non-full disk encryption drives.
    DS8000 microcode 5.4.3 is required to support data encryption.
    solid-state drives
    IBM Tivoli Storage Productivity Center supports solid-state drives for DS8000. Solid-state drives provide faster input/output (I/O) performance.
    DS8000 microcode 5.4.2 is required to support solid-state drives.
    1 TB SATA disk drives
    Tivoli Storage Productivity Center supports high-capacity SATA drives for DS8000. SATA drives are available in a 1 TB configuration (900 GB of usable capacity) offering a lower cost per GB. Higher capacity drives can reduce the number of drives required and also lower energy costs.

IBM System Storage DS8700
Tivoli Storage Productivity Center now supports IBM System Storage DS8700. The CIM agent for this storage subsystem does not support solid-state drives, full disk encryption, and FRU location. Therefore, Tivoli Storage Productivity Center will not support these features until a later release. Tivoli Storage Productivity Center also does not support the Storage Optimizer for the DS8700.

Performance management improvements
Tivoli Storage Productivity Center release 4.1.1 provides performance management improvements for metrics, thresholds, and alert definitions. For more information, search for improvements to performance metrics in the Tivoli Storage Productivity Center Information Center.

Storage Optimizer
The Storage Optimizer will now use a dynamic data model that is generated at run time rather than a static data model. This change provides more accurate utilization numbers in both analysis and optimization jobs. If the storage type is SSD (solid-state drives), the Storage Optimizer will also indicate the SSD pool in analysis and optimization jobs.

The Storage Optimizer also supports analysis and optimization jobs for the DS5000. SSD pool support for the DS5000 in analysis and optimization jobs will be available when the new LSI SMI-S Provider is supported by Tivoli Storage Productivity Center.

Advanced Brocade Discovery
The Advanced Brocade Discovery function has been removed from Tivoli Storage Productivity Center. This function uses the Brocade API. If you have a fabric that is managed by the Brocade API and do not have a Brocade SMI-S agent, install and configure the Brocade SMI-S agent to manage the fabric before or after you upgrade Tivoli Storage Productivity Center. You must install and configure the Brocade SMI-S agent to view zoning data or perform zone control through Tivoli Storage Productivity Center. When you upgrade Tivoli Storage Productivity Center, you receive a warning message if you are using the Advanced Brocade API but no Brocade SMI-S agent is configured to manage the fabric.

Discovery Library Adapter
Tivoli Storage Productivity Center provides a Discovery Library Adapter which can be used in a multiple IBM Tivoli product environments to exchange data with other Tivoli products. The data gathered by Tivoli Storage Productivity Center is put in a common data model format and written to a file using the Identification Markup Language. This file can be loaded into IBM Tivoli Change and Configuration Management database (CCMDB) so that other Tivoli products such as IBM Tivoli Application Dependency Discovery Manager or IBM Tivoli Business Service Manager can use that data.

For more information about Discovery Library Adapter, see the Information Center and search for Planning for the Discovery Library Adapter.

XIV Storage System integration of CIM agent users and device users
For the IBM XIV Storage System software release 10.2 and later, the XIV Storage System CIM agent must use user authentication credentials that are defined for the XIV Storage System system. XIV Storage System offers the option of using a Lightweight Directory Access Protocol (LDAP) repository for user authentication and authorization. For information about user authentication for XIV Storage System, see the IBM XIV® Storage System User Manual. This manual is available from the XIV Storage System Information Center at http://publib.boulder.ibm.com/infocenter/ibmxiv/r2/index.jsp. The link for the manual is labeled XCLI Reference Guide.

SAN Volume Controller
Tivoli Storage Productivity Center now supports SAN Volume Controller 5.1.0. SAN Volume Controller 5.1.0 includes the following features:
  • Maximum managed disk size is 2 TB.
  • Maximum virtual disk size is 256 TB.
  • The SAN Volume Controller hardware platform runs in 64-bit mode rather than 32-bit mode.
  • Solid-state drives can be in a SAN Volume Controller node. Solid-state drives are an optional feature for SAN Volume Controller.

Tivoli Storage Productivity Center for Replication
IBM Tivoli Storage Productivity Center for Replication 4.1.1 contains the following functional enhancements:

Using IBM TotalStorage Enterprise Storage Server 800 (ESS 800) volumes in the H1 volume role for Metro Global Mirror and Metro Global Mirror with Practice
    When performing Metro Global Mirror replication, you can use ESS 800 volumes in only the H1 volume role. You can also mix ESS 800 and DS8000 volumes in the H1 volume role. All other volume roles must use DS8000 volumes.

    Note: Because ESS 800 does not support the Incremental Resync (IR) function, a full copy is required when transitioning from H1>H2>H3 to H1>H3 and from H2>H1>H3 to H2>H3.
z/OS connections without the need for TCP/IP connectivity
    The IBM Tivoli Storage Productivity Center for Replication management server that runs on z/OS can now connect to IBM storage systems through a z/OS connection. The z/OS connection is used to issue replication commands and queries to attached extended count key data (ECKD™) volumes. The commands and queries are sent over an existing FICON® fabric, which is also used to receive asynchronous events.
    The z/OS connection is limited to storage systems that are connected to z/OS systems that are running an IBM Tivoli Storage Productivity Center management server.
    New and enhanced CLI commands are available to manage z/OS connections:
    addstorsys
    Adds a specific storage system and its volumes through a z/OS connection.
    chlocation
    Changes the location associated with specific storage systems.
    lsdevice
    The lsdevice command (which lists attributes of storage subsystems) has been enhanced to include z/OS as a connection type (in addition to direct connect, and hardware management console (HMC)).

    lsstorcandidate
    Lists storage systems that can be discovered through the z/OS connection.
    rmstorsys
    Removes a specific storage system and its volumes that are attached through a z/OS connection.
    showdevice
    The showdevice command (which lists attributes of a single storage subsystem) has been enhanced to include z/OS as a connection type (in addition to direct connect, and hardware management console (HMC)).


Connection management
    The Storage Systems panel has a new Connections page. This page lists all connections and the storage systems behind each connection. It also displays the connection status and connection type.

Storage system locations
    You can set or change the location of a storage system that has been added to the Tivoli Storage Productivity Center for Replication configuration from the Storage Systems panel under the Location column in an editable drop-down field. You can no longer set the location when adding a storage system or connection.
    From the CLI, you can use the chlocation command to change the location of a storage system that has been added to the Tivoli Storage Productivity Center for Replication configuration.
    Note: The -location parameter has been deprecated and therefore removed from the documentation for the adddevice, addmc, and rmmc commands. Use the chlocation command to set the location for a storage system.

Metro Mirror sessions with HyperSwap® capabilities
    On IBM System z®, you can now create Metro Mirror (with failover/failback) sessions that have HyperSwap capabilities. Enabling HyperSwap when Tivoli Storage Productivity Center for Replication is installed on System z combines an availability solution with a business continuity solution.

    Using the Metro Mirror with HyperSwap sessions means that, if an error occurs on a primary device, z/OS will redirect I/O requests to the secondary devices (for example, HyperSwap), thereby masking the application and the system from the I/O error.

    If an error occurs on a secondary device, or on a replication link between primary and secondary devices, a freeze occurs, ensuring that the target site remains consistent. This allows the customer to recover at the secondary site if the link failure was actually the start of a primary site failure.
Backing up the database
    If you are using the zero-administration embedded repository (not DB2®) as the persistent datastore for the Tivoli Storage Productivity Center for Replication database, you can back up the database from the CLI using the new mkbackup command.

Port connections
    The standby management server port is used for communication between the active and standby management server. You can initially set this port at installation time. You can view the current port for each management server from the graphical user interface (GUI) by clicking Management Servers from the navigation tree pane, or from the CLI using the lshaservers command.

    The client port is used to log on to the graphical user interface and command line interface from a remote system. You can initially set this port at installation time, as well. You can view the client port number on the local management server by clicking About from the navigation tree pane.

    You can also modify the standby management server and client ports after installation.

    Important: The standby management server port number must be the same on both management servers in a high-availability relationship. The client port number must also be the same on both servers. If you change either port number on one management server, you must also change it on the other.

Installation graphical user interface (GUI) change
    The Tivoli Storage Productivity Center for Replication Defaults port panel checks for port conflicts on ports 5110 and 5120. If there is a conflict, a new port is assigned by increasing the port number and then retesting for a port conflict until an available port is found. You can also specify a different port number at installation time.
1.8 Installing, upgrading, or migrating IBM Tivoli Storage Productivity Center Version 4.1.1

When installing, upgrading, or migrating to IBM Tivoli Storage Productivity Center Version 4.1.1, follow the instructions in IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication Installation and Configuration Guide

Note:
IBM Tivoli Storage Productivity Center Version 4.1.1 is only available in English. There are no language packs available for this version of the product. See issue 46187.

1.9 Using Tivoli Storage Productivity Center

This section provides additional information about how different components work when used with Tivoli Storage Productivity Center.

SLP Discovery
    One method for automating the discovery of devices is to use Service Location Protocol (SLP). However, a common problem with SLP discovery is due to IP multicasting being disabled on the network router. Communication between the SLP Service Agent and User Agent is done with IP multicasting. There are two recovery procedures when there are SLP discovery problems and IP multicasting is disabled on the network router:
    1. Configure one SLP Directory Agent for each subnet within the environment.
    2. Enable IP multicasting on the router, which is actually disabled by default. The following are the common router configurations for multicasting:
    • Internet Group Management Protocol (IGMP) is used to register individual hosts in particular multicast groups and to query group membership on particular subnets.
    • Distance Vector Multicast Routing Protocol (DVMRP) is a set of routing algorithms that use a technique called Reverse Path Forwarding to decide how multicast packets are to be routed in the network.
    • Protocol-Independent Multicast (PIM) comes in two varieties: dense mode (PIM-DM) and sparse mode (PIM-SM), that are optimized to networks where either a large percentage of nodes require multicast traffic (dense) or a small percentage require the traffic (sparse).
    • Multicast Open Shortest Path First (MOSPF) is an extension of OSPF. It is a link-state unicast routing protocol that attempts to find the shortest path between any two networks or subnets to provide the most optimal packet routing.

1.10 Known limitations

This section lists known limitations when using IBM Tivoli Storage Productivity Center. Also check the following Web site for IBM Tivoli Storage Productivity Center limitations:
http://www-01.ibm.com/software/sysmgmt/products/support/IBMTotalStorageProductivityCenterStandardEdition.html


SAN Volume Controller with more than 10,000 VDisk maps might cause probes to fail
    IBM Tivoli Storage Productivity Center data probes may fail against SAN Volume Controllers running 4.3.1.x or 5.1.0.0 when there are more than 10,000 host-VDisk maps. To correct the problem, upgrade the SAN Volume Controller cluster to level 5.1.0.1 or later.

Hitachi Data Systems CIMOM limitation
    The correlation between LUNs created on virtual storage with the virtual disks that those LUNs are created on cannot be displayed because of a CIMOM limitation. However the correlation of LUNs created on local storage of the virtualizer and the local disks is supported. All reports that show this correlation and also reports correlating host assigned LUNs with virtual disks will contain only local storage LUNs.

Hitachi Data Systems performance monitoring
    Starting with HiCommand Device Manager v6.1, the HDS SMI-S providers support basic performance statistical data for some families of HDS storage subsystems. For more information regarding Tivoli Storage Productivity Center support for HDS systems,
38553
    A fabric probe fails for a Brocade fabric when an SMI-S Agent is managing the fabric.
    Possible Cause: A non-standard FA_HOST exists in the zoning configuration.
    FA (Fabric Assist) Zone is an old legacy feature and discontinued starting from the Brocade FOS 5.3 release. This was originally designed, like Brocade QuickLoop, to allow new customers with legacy non-FC capable equipment to take advantage of FC zoning capabilities. Commands to create and modify FA Zones and QuickLoops were subsequently dropped from the Brocade switch CLI. The Brocade switch CLI cfgshow command would still passively recognize such features if they were created from older legacy switches in the fabric.
    The Brocade SMI-S Agent will return exceptions while discovering zone configurations which would contain FA_HOST as members.
    To identify if you have FA_HOSTs as members, run the Brocade switch cfgshow command and look for WWN members with brackets around them, such as: H{210000E08B841E1B}.

    Work around:
    1. Telnet to the switch.
    2. Delete the alias or zone containing the FA_HOST using the Brocade switch alidelete command or zonedelete command, respectively.
    3. Save the configuration changes using the cfgsave command and enable the same using the cfgenable command.
43945
    The Volume planner may not reuse an existing unassigned volume on ESS storage subsystems even if the "Use existing unassigned volumes (if available)" option is selected. The Volume planner creates a new volume instead of reusing an existing one.
45658
    In the topology viewer, clicking the expansion button (the plus sign) in the Group column of the tabular view will display the members of that group. Very infrequently, multiple members of that group will be selected when the group expands. This does not affect the functions that can be performed on those group members.
45923
    If two different versions of a CIMOM are being used to obtain data from a DS4000 or DS5000 device, the older version of the CIMOM should be removed to assure that the functionality of the newer version of the CIMOM is used. IBM Tivoli Storage Productivity Center does not provide a method for specifying the order in which CIMOMs are used to obtain data in these environments.
    46084
      An authentication error can occur when Tivoli Storage Productivity Center is installed using OS Authentication in Domain, if the same user ID also exists as a domain user.
      46169
        When upgrading from Tivoli Storage Productivity Center v4.1.0 to v4.1.1, there are several installation panels that the user will not see. These include the Tivoli Integrated Portal (TIP) installation panel and the Lightweight Directory Access Protocol (LDAP) installation panel. This is because these components are already installed by the v4.1.0 installer. However, new v4.1.1 installations will walk the user through these panels.
        46187
          After you upgrade Tivoli Storage Productivity Center from version 3.3.2 or 4.1 to version 4.1.1 and have previously installed the Language Pack, you must reinstall the Language Pack after an upgrade.

          Note: Any new or changed information in version 4.1.1 will appear in English only.

          If you are upgrading Tivoli Storage Productivity Center from version 4.1 to 4.1.1, only the Language Pack for the Device server needs to be installed. If you are upgrading from TotalStorage Productivity Center version 3.3.2 to 4.1.1, then the Language Pack for all the components needs to be installed.

          ***53733
          In order to see and access the Management Servers option on the Tivoli Storage Productivity Center for Replication menu, you must have Tivoli Storage Productivity Center for Replication Two Site Business Continuity installed.

        1.11 Known issues

        This is a list of known issues that have not been fixed.

        Alert Window help panels should list TEC/OMNIbus as a selectable option for Triggered Actions
        The help panels for the various nnn Alerts - Alert Window product panels should list TEC/OMNIbus as one of the triggered
        actions. Currently they list only TEC as the triggered action. This does not affect the function of the product.
          Note: nnn refers to the type of alert.
        IC63652
          When upgrading from Tivoli Storage Productivity Center 4.1 to 4.1.1, the database upgrade schema fails when upgrading the database using other languages besides English.
          Replace the DB2 message file db2clp.mo from the language-specific directory with msg/en_US.iso88591/db2clp.mo. Do this only at the time of the upgrade. After the upgrade, restore the original message file.

        IC64141
        *** IC64793
          Use the GNU tar program rather than the native AIX tar program to extract files from Tivoli Storage Productivity Center installation images. The AIX tar program might truncate long file names, which can cause errors in Tivoli Storage Productivity Center and Tivoli Integrated Portal installation.
        IC65410
          The historical fabric zoning data gets deleted from the database during an upgrade to TPC 4.1.1.55 (the initial release of Tivoli Storage Productivity Center) or to TPC 4.1.1.61 (fix pack 1). Because it is deleted during an upgrade, the historical fabric zoning changes will not be displayed in the Configuration History feature.
          This issue will be resolved in APAR IC65410 which is targeted for fix pack 2. You can avoid the deletion of historical fabric zoning data by directly upgrading to TPC 4.1.1 fix pack 2 (instead of upgrading to an earlier version of Tivoli Storage Productivity Center 4.1.1).
          This fix is not retroactive. If an upgrade is done without this APAR fix, the zone information in the snapshot cannot be retrieved.

        36227
          Frequent progress polling from Tivoli Storage Productivity Center for Replication can cause the ESSNI agent running on DS8000 clusters or DS6000 clusters to stop responding to Copy Services queries and commands. To recover from this, a Customer Engineer must restart the ESSNI agent on the clusters.

          Work around:
          Adjusting the progress polling performed by Tivoli Storage Productivity Center for Replication helps avoid this problem. If you adjust the progress polling, the Progress Reporting feature shows only 0% or 100% progress. To modify the progress polling interval, perform the following steps:

          1. Find the rmserver.properties file under the Tivoli Storage Productivity Center for Replication installation directory <TPC-R_base_directory>/profiles/CSM/properties/rmserver.properties.
          2. Open the file for editing and add the following lines at the end of the file:
          csm.server.progress.query.interval.max=31536000
          csm.server.progress.query.interval.initial=31536000
          csm.server.progress.query.interval.min=31536000
          csm.server.progress.query.interval.step=31536000

          Ensure that you do not change any other properties when editing this file. This will set the progress polling to an interval of 31,536,000 seconds, or approximately one year, effectively forcing the progress querying to turn off.

          A DS8000 firmware fix for this is being developed and the minimum level of microcode needed for Tivoli Storage Productivity Center for Replication will be updated on the Supported Products List matrix support Web site after it is available. After you install a DS8000 firmware fix, you can safely undo the changes made to the rmserver.properties file. Undoing the changes to this file will enable regular Progress Reporting status updates.
        37308
          There is a known problem that occurs when you suspend sessions that contain ESS 800 machines in the H1 role. If you issue a suspend event while running any session with ESS 800 in the H1 role of Metro Mirror pairs, then all pairs are marked as suspended. It is possible that some full-duplex events could be generated, which will cause some pairs to be marked as prepared.

          At this point, if you attempt to perform a recovery operation, Tivoli Storage Productivity Center for Replication will display the session as inconsistent. If the suspend command is successful, the data on the secondary site will be consistent. However, Tivoli Storage Productivity Center for Replication will incorrectly report this as inconsistent. If you wait for the suspend events to be processed before you issue a recovery operation, or wait approximately 10 minutes and then issue a refresh pair states command, the pairs will show the correct state of suspended, but will still be flagged as inconsistent, even though they might actually be consistent. If this occurs, verify that the suspend command completed successfully while all pairs were prepared. Then, validate the consistency of the data on the secondary site.

        45055.NF
          The Port Peak Send/Receive Data Rate metric values reported in Tivoli Storage Productivity Center for Brocade switches at a code level earlier than FOS 6.2.2 are incorrect. The switch under-reports the data rate values by a factor of 4, as visible in the Fabric Manager > Reporting > Switch Performance > By Switch and By Port reports. Please reference Brocade Tracking ID TR000264662 for the solution to this issue.

        45059
          Opening multiple L0 topology views along with other GUI panels can result in the L0 topology views not refreshing automatically. Clicking on the tabs of the L0 topology views will refresh those views. The Refresh Tabs and Refresh All Tabs functions do not refresh these views. This is a limitation of the JRE 1.5 runtime environment, and will be resolved when the product is moved to the JRE 1.6 runtime environment.

        45113
          The Port Send/Receive/Overall Utilization Percentage metric values reported in Tivoli Storage Productivity Center do not properly indicate a port performance bottleneck for IBM ESS storage subsystems. The user might be unable to appropriately set the threshold values for this metric, and as a result might receive unexpected and false alerts in Tivoli Storage Productivity Center.

        46025
          The Read Cache Hit Percentage metric value reported in Tivoli Storage Productivity Center might exceed 100% for EMC storage subsystems. The EMC SMI-S provider in rare cases over-reports the number of read cache hits, as visible in the Disk Manager > Reporting > Storage Subsystem Performance > By Storage Subsystem report. However the Read Cache Hit Percentage values in the By Volume report should be accurate.
        46046
          Performance monitors for DS8000 storage subsystems at a microcode level earlier than 5.4.3.52 might fail in Tivoli Storage Productivity Center 4.1.1. The storage subsystem reports invalid metric values which can cause errors in the performance statistics collection, or can cause errors when attempting to display the performance reports.

        46114
          In rare cases the By Controller report ( Disk Manager > Reporting > Storage Subsystem Performance > By Controller) might fail to display properly in Tivoli Storage Productivity Center 4.1.1. The following error message is displayed instead: GEN7022E: A server error occurred while retrieving performance data.

        46150
          This issue refers to the L2 Computer view in the topology viewer. For any Computer with an HBA interface installed and the HBA ports connected to the fabric, the Connectivity Group of the selected computer shows the HBA boxes for each individual HBA WWPn containing 0 used/0 unused FCPports. Therefore, no FCports exist for that specific HBA WWPn. The expected HBA FCPorts appear under Connectivity Group under FCPorts box, a separate box, and not inside of any HBA boxes above. This is an incorrect behavior. The fibre connection of any selected FCport inside of FCPorts box to their Switches can be displayed in the L2 Computer view > Connectivity view as expected.
          This issue also refers to the Data Path Explorer view of any assigned volume of the Computer with the Fabric agent installed. The Data Path Explorer view of the volume does not contain an HBA box under Initiator Entities box; it shows the FCPorts box instead of the HBA box. This is an incorrect behavior. The user cannot identify which HBA corresponds to those ports if multiple HBA cards exist on the system.

        46171
          The service.sh script on /opt/IBM/TPC/service for a remote Fabric agent does not work.

        46178
          The Tivoli Storage Productivity Center splash screen in Tivoli Integrated Portal has the wrong version number after an upgrade.

        46260
          When upgrading from TotalStorage Productivity Center version 3.3.2 to Tivoli Storage Productivity Center 4.1.1, the role to group mapping fails. This occurs when you have LDAP configured. This issue is a display issue only; the new entered groups are saved correctly.

        46271
          The procedure for changing the authentication method from operating system to LDAP did not work. See the doc_corrections_v11.pdf below. Search for 46271.
        46462
          The Tivoli Storage Productivity Center installation program is unable to run in graphical mode on Red Hat Enterprise Linux AS Version 4 and 5 or SUSE Linux Enterprise Server version 9 and 10. You must install a Linux RPM package on these operating systems. For more information, see http://www-01.ibm.com/support/docview.wss?uid=swg21303823.

        *** 46637
          IBM Tivoli Storage Productivity Center reports: disk space values for storage subsystems and spare disks Tivoli Storage Productivity Center calculates disk space totals for storage subsystems with and without spare disks on different reports.
          The values for the Disk Space and Available Disk Space columns in the following reports do not include spare disks in their calculations:

          Data Manager > Reporting > Asset > System-wide > Storage Subsystems > By Storage Subsystem
          Data Manager > Reporting > Asset > System-wide > Storage Subsystems > By Disk Space
          Data Manager > Reporting > TPC-wide Storage Space > Disk Space > By Storage Subsystem
          Disk Manager > Reporting > Storage Subsystem > Disks > By Storage Subsystem

          The values in the TOTAL row for the Disk Space and Available Disk Space columns on the following reports include spare disks in their calculations:

          Data Manager > Reporting > TPC-wide Storage Space > Disk Space > By Disk
          Disk Manager > Reporting > Storage Subsystem > Disks > By Disk

          The online help for these reports will be updated in the next release of Tivoli Storage Productivity Center.
        *** 47004
          Tivoli Storage Productivity Center is unable to unassign volumes from a Hewlett Packard EVA device. To unassign volumes on this device, use the Hewlett Packard EVA element manager.
        *** 49368
          A storage optimization report for a storage system that contains multiple pools with the same name will automatically include all those pools if one is selected for the report. For example, if multiple storage pools have the same name and you select one of those pools as a source entity for an optimization report, all the pools with that name are also included as source entities for the report.

          To avoid selecting multiple pools with the same name when using the Storage Optimizer, make sure to assign unique names for the storage pools in the storage systems that you want to optimize.
        *** IC70486 (52633)
          Tivoli Storage Productivity Center for Replication cannot be started from Tivoli Storage Productivity Center when using LDAP authentication with 4.1.1.95 (FP4) and higher.

          Work around:
          Make a copy and rename your Tivoli Integrate Portal user’s preference folder. The user preference directories are in the following directory:

          <TIP_Install_Dir>/profiles/TIPProfile/config/cells/TIPCell/applications/
          isclite.ear/deployments/isclite/isclite.war/WEB-INF/isc.dir

          Find your user’s directory, make a copy of it in the same directory and rename it to use the short username.

          For example, if your LDAP user is “TPCSuperuser”, the existing directory name might be
          “UID=TPCSUPERUSER,CN=LDAPREALM,O=IBM,C=US”. Make a copy of this directory and rename it to
          “TPCSUPERUSER”. If you have multiple LDAP users, contact L2 for a patch.
        ***IC71244 (37745)
          When installing Tivoli Storage Productivity Center for Replication, InstallShield can cause the installation to hang at
          the end of the installation process. If the installation has completed, stopping the process should not adversely
          affect the installation and Tivoli Storage Productivity Center for Replication will work as expected. The installation
          has completed if you see the "success" panel at the end of installation or the following message at the end of the
          TPCRMInstall.log:

          Install, com.installshield.project_1.event.dialog.swing.PanelPostInstallSummary, dbg, Original summary message =
          The InstallShield Wizard has successfully installed $P(displayName).
          Choose Finish to exit the wizard.

          If this describes your situation, you should kill the setupwin32.exe process using the Windows Task Manager. The
          main installation should complete at that time.

          Alternatively, you click Cancel, but this may exit you from the entire installation.
        ***53725
          When running the Service tool for the agents, you receive this message: "Starting TPC 4.1.1 Fabric Agent Service Program." However, the service script does not complete processing and you do not get the logs for the agents. This could be a result of a deadlock when running the service script.

          Work around:
          Stop the Tivoli Common Agent before running the service script.
        ***IC75734 (43310)
          The table in topic "scheduler.config" file in the Information Center should include the following parameter for the scheduler.config file:

          Parameter: delayLimitMinutes

          Description: The number of minutes after a scheduled job start that the Scheduler will continue to attempt to launch the job to a specified resource. Note: Resource state must not be "down" and connection status must not be "failed".
        ***IC76035 (53696)
          Attempting to launch the Tivoli Storage Productivity Center GUI from the TIP console fails due to an extra slash (/) character in the URL between ITSRM and app.

          Example: http://your_IP:9550/ITSRM//app/tpcgui.jnlp

          Work around:
          Use Java WebStart to launch the Tivoli Storage Productivity Center GUI:
          https://your_IP:9550/ITSRM/app/en_US/index.html[

          or

          Launch a new browser tab in the TIP GUI and correct the URL by removing the extra slash:
          http://your_IP:9550/ITSRM/app/tpcgui.jnlp

        1.12 Documentation corrections

        Cross reference information
        Segment Product Component Platform Version Edition
        Storage Management Tivoli Storage Productivity Center Basic Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 4.1.1 All Editions
        Storage Management Tivoli Storage Productivity Center for Data Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 4.1.1 All Editions
        Storage Management Tivoli Storage Productivity Center for Disk Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 4.1.1 All Editions
        Storage Management Tivoli Storage Productivity Center for Replication Not Applicable AIX, Linux, Windows, z/OS 4.1.1 All Editions
        Storage Virtualization Software System Storage Productivity Center Not Applicable AIX, Linux, Windows 1.4 N/A

        Rate this page:

        (0 users)Average rating

        Add comments

        Document information


        More support for:

        Tivoli Storage Productivity Center Standard Edition

        Software version:

        4.1.1

        Operating system(s):

        AIX, HP-UX, Linux, Solaris, Windows, z/OS

        Software edition:

        All Editions

        Reference #:

        1406484

        Modified date:

        2014-07-12

        Translate my page

        Machine Translation

        Content navigation