Preventive Service Planning
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.
1.1 Installing, upgrading, or migrating Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication Version 4.2
1.2 Known issues in related products
1.3 Known issues for Tivoli Storage Productivity Center
1.4 Known issues for Tivoli Storage Productivity Center for Replication
1.5 Documentation corrections
***Note: Recent changes to this flash are indicated by asterisks (***).
1.0 Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication Flash for Version 4.2
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 and IBM Tivoli Storage Productivity Center for Replication User's Guide
Access the IBM Tivoli Storage Productivity Center Information Center here:
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:
1.1 Installing, upgrading, or migrating IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication Version 4.2
When installing, upgrading, or migrating to IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication Version 4.2, follow the instructions in IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication Installation and Configuration Guide.
For information about installing or upgrading IBM Tivoli Storage Productivity Center for Replication for System z, see IBM Tivoli Storage Productivity Center for Replication for System z Installation and Configuration Guide.
For Tivoli Storage Productivity Center, if you use DB2 9.7, use the version of DB2 shipped with Tivoli Storage Productivity Center. Do not use DB2 9.7 with Fix Pack 1 or Fix Pack 2 (these fix packs cause issues with Tivoli Storage Productivity Center).
*** If you want to use DB2 9.7 Fix Pack 3a, you can apply a hotfix for this support. For information about this hotfix, see http://www-01.ibm.com/support/docview.wss?uid=swg24029229 .
Tivoli Storage Productivity Center 4.2 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:
To resolve this issue, use DB2 9.5 with Fix Pack 4 or DB2 9.7 base version (do not use DB2 9.7 with Fix Pack 1 or Fix Pack 2).
1.2 Known issues in related products
This section lists known issues in related products when using IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication. Also check the following website for other known issues in related products:
Hitachi Data Systems CIMOM limitation
The correlation between LUNs created on virtual storage with the virtual disks on which those LUNs are created 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.
LSI SMI-S Provider 1.3 does not completely support indication filters
Because the LSI SMI-S Provider does not completely support indication filers, indications are not always received by Tivoli Storage Productivity Center. This can result in incomplete or no data being returned from the provider. A warning message will display when a discovery is run on the LSI SMI-S Provider 1.3. To see updates to the subsystem configurations such as create or delete volumes, and capacity changes, the subsystem should be probed using the most current LSI CIMOM.
For Tivoli Storage Productivity Center for Replication, if Open HyperSwap® is enabled for a session, the AIX® host might not be able to access the primary storage site if the MS/VCR program that is used with IBM System Storage® DS8000® receives a large number of tasks. The host will swap input/output (I/O) to the secondary storage site.
To avoid this problem:
- Limit high I/O stress or configure ports for both host and peer-to-peer remote copy (PPRC).
- Do not let the host link adapters lose connection or power while stress I/O is running.
When Tivoli Storage Productivity Center is configured on a Windows 2008 R2 with a Storage Resource agent, the switch does not show connectivity and the fabric is not discovered. You must apply a fix from Microsoft. The fix is available at http://support.microsoft.com/kb/978949/ . Install this fix to the Windows 2008 R2 servers running the Storage Resource agent.
When the Brocade SMIS Agent Configuration tool tries to add a second switch for a fabric that already has a proxy agent, this switch stays in the Login Progress state and cannot be removed.
If you encounter a problem while adding the proxy switch (get the “Login progress” message for a long time) or while removing the proxy switch (you receive the “logout failed” message) through the configuration tool, remove the proxy entry manually from the provider.xml file in the following directory:
Restart the agent.
The Remove button does not remove a newly added IP address for the Brocade SMIS Agent. You must go to another node in the navigation tree and then back to the Agent Configuration > Fabric Connections > Proxies panel. This is the behavior of the Brocade SMIS Agent Configuration tool.
The online help does not include descriptions for values on the Hosts Paths page of the Virtual Disk report for SAN Volume Controllers. This report is available in the following location in the navigation tree: Data Manager > Reporting > Asset > By Storage Subsystem > SAN Volume Controller > Virtual Disks > name of virtual disk > Host Paths tab.
The following field descriptions will be added to the online help for the Host Paths page in a subsequent release of Tivoli Storage Productivity Center:
- Controller: Name of the controller to which the disk drive is attached.
- Instance: SCSI Identifier of the SCSI address of the attached disk drive.
- Bus Number: Bus number of the SCSI address of the attached disk drive.
- Target Identifier: Target identifier of the SCSI address of the attached disk drive.
- Logical Unit Number: LUN identifier of the SCSI address of the attached disk drive.
When installing DB2 9.5 Fix Pack 4 on AIX 6.1, you receive the following error message:
The UID specified for the user "108" is invalid.
Db2setup encounters this error during the DB2 instance owner creation or das user creation.
Install DB2 Fix Pack 4 using db2_install and create the DB2 instance using db2 CLP on AIX 6.1. For information about installing DB2 on AIX, see http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp?topic=/com.ibm.tpc_V42.doc/fqz0_t_installing_db2_on_aix_cli.html.
*** For more information about this issue, see DB2 APAR IC71428.
You cannot open the Data Path Explorer view for a computer using the Storage Resource agent on HP-UX 11iv3 on Itanium unless you have probed the HP-UX Storage Resource agent with an HBA driver at the correct level. Please ensure you have version B.11.31.1009 or later of the Fibre Channel Driver using the following command:
swlist | grep -i FibrChanl-01
*** This issue has been fixed for HP-UX 11iv3 on Itanium. The fix is for the Fibre Channel Driver B.11.31.1009 as part of the HP-UX Fusion 1009 release.
When performing provisioning actions on a DS8000, Tivoli Storage Productivity Center performs a number of checks to verify that the DS8000 ESSNI server is returning realistic information. One such check is to ensure that the ESSNI server does not return multiple instances of a single entity (such as an extent pool). If Tivoli Storage Productivity Center encounters such an error it will fail the current provisioning action and log the error in the appropriate job log. These issues are rare and intermittent -- found primarily at times when the ESSNI server's performance is degraded. If the cause of this degradation is known, fix the degradation problem and then, after performing any necessary cleanup from the failed provisioning task, retry the desired Tivoli Storage Productivity Center provisioning tasks. If the cause is not known, either restart the ESSNI server on each CEC or else wait a while before retrying.
It is important to note that these issues, though rare in all cases, are most likely to occur when running older microcode levels. If the problem is encountered, please make sure that the DS8000 is running the latest microcode.
When using Tivoli Provisioning Monitor 7.1.1 or 7.2 with Tivoli Storage Productivity Center, the Tivoli Provisioning Monitor GUI does not display the correct active zoneset for fabrics with multiple zonesets defined. The active zoneset listed is always the first one retrieved from the DCM. This is a Tivoli Provisioning Manager GUI issue only. Tivoli Storage Productivity Center knows the correct active zoneset and will display it in the Tivoli Storage Productivity Center GUI. It is important to note that most Tivoli Storage Productivity Center fabric workflows operate in the active zoneset. Because Tivoli Storage Productivity Center knows the correct active zoneset, it will perform the requested actions correctly. However, the information might not be displayed properly in Tivoli Provisioning Manager until after the next run of the Tivoli Storage Productivity Center discovery workflow.
1.3 Known issues for Tivoli Storage Productivity Center
This section lists known issues when using IBM Tivoli Storage Productivity Center. Also check the following website for other IBM Tivoli Storage Productivity Center issues:
The Storage Resource agent cannot be deployed on the Solaris machine and the initial probe fails. This issue occurs only for Solaris machines with solid state drives attached. Contact IBM support for a temporary fix.
Probe jobs for NAS filers configured as "Other NAS" filers and being probed by a Windows Storage Resource agent do not correctly report the filer volumes. Probe jobs for NAS filers configured as "Other NAS" filers and probed by UNIX Storage Resource agents work properly. volumes.
If you want a temporary fix for the Windows Storage Resource agent, contact IBM support.
Tivoli Storage Productivity Center cannot probe DS8000s containing LCUs (logical control units) which are configured but empty (for example, the LCUs have zero volumes). Probe attempts will fail with the following job log error message:
HWNEP0134E Following exception occurred: com.ibm.tpc.ep.base.EPHdlrRunException:
com.ibm.storage.ess.ni.exception.NIParameterInvalidServerException: completionStatus = 2, parameterClass =
class [Lcom.ibm.storage.ess.ni.identifiers.NIVolumeID;, Additional info: .
If this scenario is encountered, and there are no plans to create volumes on the LCU or LCUs in the near term, the recommended action is to delete the empty LCU(s). From a DSCLI, run the command lslcu to list the LCUs configured on the DS8000. For each that is listed as having 0 volumes, delete it by running the command rmclu. If these empty LCUs are necessary for an extended period of time (for example, to reserve certain addresses), please contact IBM support to receive a temporary fix to allow Tivoli Storage Productivity Center to properly handle these LCUs.
If you want a temporary fix for this issue, contact IBM Software Support.
When you migrate an in-band Fabric agent to a Storage Resource agent, you see discrepancies in HBA report information.
When you migrate an in-band Fabric agent to a Storage Resource agent on an AIX host, this operation results in double entries for the HBAs in that host with different names for each. The HBAs originally found by the in-band Fabric agent are marked missing while new ones appear as a result of the Storage Resource agent. The agents report different names because of different protocols used to get the information.
This example displays the expected behavior:
Storage Resource agent:
In-band Fabric agent:
Because of an existing issue, the missing HBAs cannot be removed from the database with the Remove from Database option or with Removed Resource Retention.
You can ignore the missing HBA or contact IBM support for a procedure to clean up the missing HBA from the database. Resolving this issue varies on a case-by-case basis.
Note: Missing HBAs are ignored and do not cause any negative side effects to normal Tivoli Storage Productivity Center processing.
The scan job log for the Storage Resource agent does not log the file system profiles or constraints in the scan job log like the Data agent. The user will not be able to distinguish the different selections between the file system scan jobs on the agent computer or the NAS filers or both.
The online help for some reports indicates that some columns do not contain values for SAN Volume Controller. This is no longer true. Tivoli Storage Productivity Center now calculates values for SAN Volume Controller in the following report columns: Overhead, Formatted Space, Formatted Space with No Volumes, Assigned Volume Space, Unassigned Volume Space, and zOS Volume Space.
These columns are displayed in the following reports:
- IBM Tivoli Storage Productivity Center > Reporting > Rollup Reports > Asset > Storage Subsystems: By Storage Subsystem, By Disk Space, By TPC Server
- IBM Tivoli Storage Productivity Center > Reporting > Rollup Reports > Asset > Storage Subsystem Volumes > By Storage Subsystem, By Storage Subsystem Volume Space
- Data Manager > Reporting > Asset > System-wide > Storage Subsystems > By Storage Subsystem, By Disk Space
- Data Manager > Reporting > TPC-wide Storage Space > Disk Space > By Storage Subsystem
In the next release of Tivoli Storage Productivity Center, the help topics for these reports will be updated to indicate support for SAN Volume Controller.
Uninstalling Tivoli Storage Productivity Center on Windows 64-bit does not always uninstall Tivoli Storage Productivity Center for Replication. To uninstall Tivoli Storage Productivity Center for Replication manually, see http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp?topic=/com.ibm.tpc_V42.doc/fqz0_t_manual_uninstall_win.html.
If you have a Tivoli Storage Productivity Center V4.2 system installed, you cannot install a Data agent or Fabric agent from a V4.1.1 (or earlier) release on the V4.2 system.
Uninstalling the Storage Resource agent using the Tivoli Storage Productivity Center uninstallation wizard requires a reboot of the Windows operating system.
After you install the Tivoli Storage Productivity Center server with LDAP authentication (excluding the Storage Resource agent), then run the installation wizard to install the Storage Resource agent, you receive a message that OS authentication is specified. The installation wizard instructs the user to define group-to-role mapping.
When you create a performance monitor job and you specify the job to "continue indefinitely" for duration, the "next run" column displays a value of "on demand."
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.
When you migrate a Data agent or Fabric agent to a Storage Resource agent, you see warning messages in the migration log indicating that you need to delete a directory manually. However, the directory has been removed and the migration is successful.
The SAN planner completed with a warning message because of a set multipath policy failure of 12 even when volumes where successfully assigned and surfaced on the host.
Computer scan definitions are not removed from Tivoli Storage Productivity Center after the Storage Resource agent was removed. Refreshing the scan node has no effect.
Delete the scan definition manually.
When you create a zone with a name that already exists using tpctool, there is no warning or error message for the zone. The commit failed with the following error message:
The commit failed with error AAJ003000E
Note: The Tivoli Storage Productivity Center CLI error messages are not translated. Messages received from the Tivoli Storage Productivity Center server are translated as appropriate. However, messages directly from the tpctool command are in English only.
Tivoli Storage Productivity Center does not support the multipath I/O driver for XIV®. As a result, you will see Tivoli Storage Productivity Center topology and reports displaying only one path to the XIV storage system.
Error message SRV085400E occurs when trying to create a volume on a DS4000® storage system. This is caused by a connection time out to the SMI Agent that is managing the storage system. Restart the SMI Agent and try to create the volume.
This issue occurs intermittently and can be resolved by restarting the CIMOM.
When using the SAN Planner and you specify a candidate Storage Resource Group (for example, storage subsystem s1), and also implicitly select a volume from a pool of storage subsystem s1 (for example, pool1), pool1 is not considered a candidate.
The online help for creating fabric performance reports does not describe all the options that are available for filtering the data in those reports. Specifically, it does not describe the following options when you create a performance report in Fabric Manager:
- Display latest performance data
- Display historic performance data using absolute time
- Display historic performance data using relative time
However, this information is available in the Tivoli Storage Productivity Center Information Center and User's Guide. To view descriptions of these options, go to the Creating switch performance reports section in (Chapter 6) Reporting > User-defined online reports > Fabric Manager reports of this publication. This information will be added to the online help in a subsequent release of Tivoli Storage Productivity Center.
When using the SAN Planner wizard to provision storage with replication or provision replication to existing storage, the storage resource group (SRG) fields might be disabled on the Specifying a secondary location and Specifying a tertiary location pages. SRG fields are disabled on these pages if you did not specify an SRG in the input for the source volumes in the Specifying the Plan Content page. Additionally, the list of SRGs that are displayed on these pages contain SRGs that are not part of any existing replication sessions. If all SRGs are part of replication sessions, these input fields are disabled.
The online help for the pages in the SAN Planner will be updated in the next release to reflect this additional information.
This issue pertains to unformatted disk space for XIV storage systems.
The By Storage Subsystem reports under the Data Manager > Reporting > Asset node in the navigation tree provides detailed information about monitored storage systems. When you click a storage system, a report is displayed in the content pane. This report includes values for the unformatted disk space in storage systems. For XIV storage systems, unformatted disk space represents the physical (hard disk) space of an XIV storage system that is available for pool creation or expansion.
The online help for the By Storage Subsystem report under Data Manager > Reporting > Asset > System-wide > Storage Subsystems indicates that a value is displayed in the "Overall Unavailable Disk Space (Total Overhead)" column for IBM DS8000 storage subsystems. This is incorrect. Tivoli Storage Productivity Center does not provide a value in this column for IBM DS8000 storage subsystems.
The following columns no longer appear in the By Volume Space report Disk Manager > Reporting > Storage Subsystems > Volumes:
- VCM Database
- Detachable Mirror
The descriptions of these columns will be removed from the online help in a subsequent release.
This issue pertains to the FlashCopy® attribute for virtual disks and volumes.
The details panels for virtual disks and volumes displays the value None in the FlashCopy field if the FlashCopy session for the virtual disk or volume has not been started.
For example, navigate to Disk Manager > Storage Subsystems, select a SAN Volume Controller, and click Virtual Disks. On the VDisks report, filter the list of virtual disks and click the magnifying glass icon next to a virtual disk to view the details panel for the virtual disk. If the virtual disk is in a FlashCopy session, but the session has not been started, Tivoli Storage Productivity Center displays None in the FlashCopy field. To work around this issue, re-probe the storage system.
The online help for these reports will be updated to reflect this information.
If you have not rebooted the system after installing 64-bit DB2 V9.7 on a 64-bit Windows system, then install Tivoli Storage Productivity Center, you receive this DB2 error message: A valid database was not found.
Follow these steps:
- Open the service configuration tool (Start > run > services.msc).
- Click DB2 Management Service (copyName) service.
- Right-click the service and click Restart.
One XIV storage system can have more than one IP address. If you are already managing an XIV storage system using one IP address and then add a new device using another XIV IP address, the IP addresses of the storage system can get mixed up. However, the data being collected will not be impacted. There is no work around currently available.
When creating a volume on a DS8000 storage subsystem, the Create Volume Wizard panel under Disk Manager > Storage Subsystems > DS8000 > Volumes provides an LSS field. The description in the online help for this field has been enhanced to include information about CKD (count key data) volumes. The new description reads as follows:
LSS: Select a logical subsystem (LSS) if you want the volumes to be created on that LSS. This field is displayed if the system is DS8000. Do not select an LSS with CKD volumes. You can use Tivoli Storage Productivity Center to create Fixed Block volumes only, so selecting an LSS with CKD volumes results in an error.
The online help for the Create Volume Wizard panel will be updated in the next release to reflect this additional information.
See issue 52221.
N-Series Gateways added to Total Storage Productivity Center as "NetApp" filers report successful probes, but no monitoring data is collected. This is not a supported configuration. N-Series Gateways must be manually entered as "OtherNAS" filers with Total Storage Productivity Center through the user interface. Click Administrative Services > Configuration > Manual NAS/Netware Server Entry. Check the Add as OtherNAS option.
Monitoring results from probes can be found as "OtherNas" devices. Click Data Manager > Reporting > Asset > By OS Type > OtherNAS.
It is not possible to scan clustered file systems with a non-daemon Storage Resource agent. Because of this limitation, do not deploy non-daemon Storage Resource agents to the nodes of MSCS or HACMP nodes. Until this issue is resolved, we recommend the following:
- If you are installing new agents, install daemon Storage Resource agents.
- If you are planning to migrate existing Data agents to Storage Resource agents, migrate the Data agents to daemon Storage Resource agents.
These recommendations are limited to agents that are installed on MSCS or HACMP nodes.
If you install non-daemon Storage Resource agents on MSCS or HACMP clustered nodes, you will be able to perform probe jobs but will not be able to scan clustered file systems. Your scan job will fail with the following error message:
Agent could not be reached.
This issue is related to the synchronization rate of the VDisk mirror. When a mirrored VDisk is created through the SAN Planner, you can specify a copy synchronization rate (the default is 50%). However, the user specified value is currently ignored and the default value is taken.
You can change the synchronization rate, if needed, by using the SAN Volume Controller Element Manager or SAN Volume Controller chvdisk command.
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.
Stop the Tivoli Common Agent before running the service script.
1.4 Known issues for Tivoli Storage Productivity Center for Replication
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.
Tivoli Storage Productivity Center for Replication cannot be started from Tivoli Storage Productivity Center.
Make a copy and rename your Tivoli Integrate Portal user’s preference folder. The user preference directories are in the following directory:
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 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 users, or cannot determine the user preference directory to copy and rename, contact IBM Software Support for a temporary fix.
When the AIX host is restarted, copy sets for devices that are connected to the host remain coupled after the copy sets have been removed. To decouple the copy sets, see Copy set is displayed as coupled after the Terminate command has been issued or copy sets have been removed for an Open HyperSwap® session in the Troubleshooting and support section of the Tivoli Storage Productivity Center/Tivoli Storage Productivity Center for Replication information center at http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp. If you do not decouple the copy sets using the procedure in the information center, the device is added to the session again when the AIX host is restarted.
During the installation of Tivoli Storage Productivity Center for Replication, do not include a domain name for the Tivoli Storage Productivity Center for Replication user if the user is a local user. A domain name is required only if the user belongs to a domain.
This defect addresses the following issues that occur when you upgrade from Tivoli Storage Productivity Center for Replication 3.4 or 3.4.1 to 4.2.
Single sign-on is disabled
The single sign-on feature is disabled when Tivoli Storage Productivity Center for Replication is upgraded from version 3.4 or 3.4.1 to 4.2 on an open system.
You can enable single sign-on using either of the following methods:
- Edit the security.xml file. The file is in c:\Program Files\IBM\replication\eWAS\bin\profiles\CSM\config\cells\DefaultNode. Search for activeAuthMechanism and change the vaule to “LTPA _1” (activeAuthMechanism="LTPA_1").
- Edit the security settings using the WebSphere Application Server wsadmin tool as follows:
1. Start wsadmin using the following command:
"c:\Program Files\IBM\replication\eWAS\bin\wsadmin.bat" -conntype SOAP -lang jython
AIX and Linux:
/opt/IBM/replication/eWAS/bin/wsadmin.sh -conntype SOAP -lang jython
2. Issue the following commands shown in bold:
wsadmin> attrs = [["activeAuthMechanism", "(cells/DefaultNode|security.xml#LTPA_1)"]]
[8/26/10 9:12:58:109 CDT] 0000000a AbstractShell A WASX7090I: Executing command: "attrs =
wsadmin> AdminConfig.modify("(cells/DefaultNode|security.xml#Security_1)", attrs)
[8/26/10 9:13:03:390 CDT] 0000000a AbstractShell A WASX7090I: Executing command: "AdminConfig.modify
[8/26/10 9:13:04:968 CDT] 0000000a AbstractShell A WASX7090I: Executing command: "AdminConfig.save()"
After you have edited the security settings using either of the preceding methods, stop and restart the Tivoli Storage Productivity Center using the following commands:
c:\Program Files\IBM\replication\eWAS\bin\stopServer.bat server1
c:\Program Files\IBM\replication\eWAS\bin\startServer.bat server1
AIX and Linux:
Error messages are displayed on AIX systems
If you upgrade from 3.4 or 3.4.1 or later to 4.2 on an IBM AIX system, the following error message is displayed although the upgrade completed successfully:
An error occurred and product update failed. Look at the logs file /opt/IBM/replication/TPCRMInstall.log for details.
To verify that the upgrade was successful, search the TPCRMIntsall.log file for the following messages. If both of these messages are contained in the log file, the upgrade completed successfully.
WASX7017E: Exception received while running file "/opt/IBM/replication/Scripts/importLTPAKeys.py";
ADMU3028I: Conflict detected on port 41185. Likely causes: a) An instance of the server server1 is already running.
If you change the user authentication method for Tivoli Storage Productivity Center for Replication from local operating system to Lightweight Directory Access Protocol (LDAP) or from LDAP to local operating system, ensure that you add the following properties to the rmserver.properties file in the Tivoli Storage Productivity Center for Replication installation directory/eWAS/profiles/CSM/properties directory. The following properties assume that you have installed Tivoli Storage Productivity Center for Replication in the default directory.
csm.server.tpc_data_server.port= port number
Where port number is the port number for Tivoli Storage Productivity Center server (the default port number is 9549) and hostname.fully.qualified.domain.name.com is the fully qualified domain name for the Tivoli Storage Productivity Center server. For example, tb3226-wi.beaverton.ibm.com.
Although you are not required to modify the rmserver.properties file unless you have changed the user
authentication method after installation, you can make this modification after you complete the installation if you anticipate that the user authentication method will be changed.
To see and access the Management Servers option on the Tivoli Storage Productivity Center for Replication menu, you must have the Tivoli Storage Productivity Center for Replication Two Site Business Continuity license installed.
1.5 Documentation corrections
For documentation corrections that could not be included in the final product documentation for IBM Tivoli Storage Productivity Center and IBM Tivoli Storage Productivity Center for Replication, see doc_corrections_v42.pdf below.
|Storage Management||Tivoli Storage Productivity Center Basic Edition||Not Applicable||Windows, Solaris, AIX, HP-UX, Linux||4.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Data||Not Applicable||AIX, HP-UX, Linux, Solaris, Windows||4.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Disk||Not Applicable||AIX, Linux, Windows, HP-UX, Solaris||4.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Disk Midrange Edition||Not Applicable||AIX, HP-UX, Linux, Solaris, Windows||4.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Replication||TPC for Replication||AIX, Linux, Windows, z/OS||4.2||All Editions|