deployment guide series ibm total storage productivity center for data sg247140

ibm.com/redbooks

Deployment Guide Series:IBM TotalStorage Productivity Center for Data

Mary LovelaceAlejandro Berardinelli

Kamalakkannan JayaramanNidhi Khator

Learn the functions and reporting capabilities of TPC for Data

Install on and configure supported platforms

Includes planning and deployment information

Front cover

http://www.redbooks.ibm.com/


Deployment Guide Series: IBM TotalStorage Productivity Center for Data

June 2009

International Technical Support Organization

SG24-7140-03

© Copyright International Business Machines Corporation 2009. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

Third Edition (June 2009)

This edition applies to Version 3, Release 3.3 of IBM TotalStorage Productivity Center for Data (product number 5608-VC3).

Note: Before using this information and the product it supports, read the information in “Notices” on page ix.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiThe team that wrote this IBM Redbooks publication . . . . . . . . . . . . . . . . . . . . . xiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvJune 2009, Third Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 11.1 What is IBM TotalStorage Productivity Center . . . . . . . . . . . . . . . . . . . . . . 2

1.1.1 TotalStorage Productivity Center structure . . . . . . . . . . . . . . . . . . . . . 31.2 TotalStorage Productivity Center for Data overview . . . . . . . . . . . . . . . . . . 71.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3.1 What is new in TotalStorage Productivity Center V3.3.2 . . . . . . . . . 141.4 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.4.1 Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.4.2 Schema of interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.4.3 Data Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.4.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.4.5 Integration points with TEC and IBM Tivoli Storage Manager . . . . . 241.4.6 Tivoli Common agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.4.7 Role-based administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

1.5 Supported levels for Version 3 Release 3 . . . . . . . . . . . . . . . . . . . . . . . . . 291.6 System Storage Productivity Center (SSPC) . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.1 Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.1.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.1.2 Disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.2 Software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.2.1 Novell NetWare considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.2 NAS environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.3 VMware environment considerations . . . . . . . . . . . . . . . . . . . . . . . . 402.2.4 IPv6 considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2.3 Databases supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

© Copyright IBM Corp. 2009. All rights reserved. iii

2.3.1 Data Manager database repository. . . . . . . . . . . . . . . . . . . . . . . . . . 452.3.2 Agent Manager database repository . . . . . . . . . . . . . . . . . . . . . . . . . 452.3.3 SMS or DMS tablespace type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.3.4 Database Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.3.5 Data agent-monitored databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2.4 Pre-installation steps for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.4.1 Installable components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.4.2 Order of component installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.4.3 Server recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.4.4 Installation port requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.4.5 Supported filesystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.4.6 Supported network filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.4.7 Support for NAS/NetWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.4.8 Disk and volume group support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.4.9 Storage subsystem support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.4.10 Tape library support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2.5 User IDs and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.5.1 User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.5.2 Increasing user security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.5.3 Certificates and key files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.6 Services and service accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.7 Analyzing and defining environment requirements . . . . . . . . . . . . . . . . . . 622.8 Agent installation methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2.8.1 Local installation of the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.8.2 Remote agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.8.3 Virtual I/O Server agent installation. . . . . . . . . . . . . . . . . . . . . . . . . . 65

2.9 Interoperability namespace summary table. . . . . . . . . . . . . . . . . . . . . . . . 662.10 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 3. Installing IBM TotalStorage Productivity Center for Data . . . . 693.1 Installing TotalStorage Productivity Center . . . . . . . . . . . . . . . . . . . . . . . . 70

3.1.1 Installing Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.1.2 Installing Agent Manager on Windows . . . . . . . . . . . . . . . . . . . . . . . 713.1.3 Typical installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.1.4 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.1.5 CD layout and components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.1.6 Configuration considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

3.2 Pre-installation steps for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.2.1 Verify the primary domain name systems . . . . . . . . . . . . . . . . . . . . . 753.2.2 Activate NetBIOS settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.2.3 Using and defining user IDs and passwords. . . . . . . . . . . . . . . . . . . 79

3.3 Windows installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.3.1 DB2 installation for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

iv Deployment Guide Series: IBM TotalStorage Productivity Center for Data

3.3.2 Agent Manager installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.3.3 Install TotalStorage Productivity Center components . . . . . . . . . . . 1293.3.4 Installing the Data server, Device server, GUI, and CLI . . . . . . . . . 139

3.4 Linux installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513.4.1 Installing DB2 Version 9 on a Linux platform . . . . . . . . . . . . . . . . . 1513.4.2 Verifying the DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1693.4.3 Installing the DB2 Fix Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703.4.4 Installation of the Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 1733.4.5 Install TotalStorage Productivity Center V3.3 database schema . . 1903.4.6 Install TPC V3.3 Data server, Device server, CLI, and GUI . . . . . . 201

3.5 AIX installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2153.5.1 DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2153.5.2 Verifying the DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2343.5.3 Installing the DB2 Fix Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2353.5.4 Agent Manager installation for AIX . . . . . . . . . . . . . . . . . . . . . . . . . 2393.5.5 Install TotalStorage Productivity Center V3.3 database schema . . 2573.5.6 Install TPC V3.3 Data server, Device Server, CLI and GUI . . . . . . 268

3.6 GUI for Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2803.6.1 Launch the TotalStorage Productivity Center GUI . . . . . . . . . . . . . 281

3.7 Changing the agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Chapter 4. Configuring IBM TotalStorage Productivity Center for Data. 2874.1 Agent deployment options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

4.1.1 Local installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2884.1.2 Remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

4.2 Local installation of Data and Fabric agents . . . . . . . . . . . . . . . . . . . . . . 2894.2.1 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2894.2.2 Unattended (silent) installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

4.3 Remote installation of Data agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3064.3.1 Preparing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . 3074.3.2 Performing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . 308

4.4 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3204.4.1 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

4.5 Uninstalling the Data agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3244.5.1 Remote uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3254.5.2 Local uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3264.5.3 Remote agent uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

4.6 Upgrading the Data agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3364.7 Alert disposition (SNMP and e-mail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3414.8 Log file retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

4.8.1 Quota and constraint e-mail address rules . . . . . . . . . . . . . . . . . . . 3434.9 Scan/probe agent administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

4.9.1 Manual NAS/NetWare server entry. . . . . . . . . . . . . . . . . . . . . . . . . 345

Contents v

4.10 Configuring TPC communication to VMware . . . . . . . . . . . . . . . . . . . . 3474.11 History aggregator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

4.11.1 Data Manager NetWare tree logins. . . . . . . . . . . . . . . . . . . . . . . . 3554.12 Data Manager CIMOM logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

4.12.1 Configuring CIMOMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3564.13 Data Manager resource history retention . . . . . . . . . . . . . . . . . . . . . . . 369

4.13.1 Removed resource retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3704.13.2 Resource history retention for databases . . . . . . . . . . . . . . . . . . . 3714.13.3 Removed resource retention for databases . . . . . . . . . . . . . . . . . 3724.13.4 Adding databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3724.13.5 Configuring chargeback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Chapter 5. Operations and reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3795.1 Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

5.1.1 The user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3805.1.2 Administrative services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

5.2 IBM TotalStorage Productivity Center menu reports. . . . . . . . . . . . . . . . 3925.2.1 Predefined reports under the My Reports node . . . . . . . . . . . . . . . 3925.2.2 Batch reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4105.2.3 Probe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4135.2.4 External Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

5.3 Data Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4165.3.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4175.3.2 Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4285.3.3 Policy Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

5.4 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4505.4.1 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4525.4.2 Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4525.4.3 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4715.4.4 Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4725.4.5 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4775.4.6 Usage violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4825.4.7 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

5.5 Reporting for databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4865.5.1 Register the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4885.5.2 Set up probes and scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4905.5.3 Database capacity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4945.5.4 Database usage reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

5.6 Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5005.6.1 Pin list persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5025.6.2 Link to reports/alerts from the Topology Viewer . . . . . . . . . . . . . . . 5045.6.3 Context Sensitive Reporting and Data Path Explorer . . . . . . . . . . . 511

5.7 Enterprise Server Rollup function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

vi Deployment Guide Series: IBM TotalStorage Productivity Center for Data

5.7.1 Rollup Reporting recommendations . . . . . . . . . . . . . . . . . . . . . . . . 5165.7.2 Creating Rollup reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5185.7.3 TotalStorage Productivity Center server probe process . . . . . . . . . 5215.7.4 Generating TotalStorage Productivity Center V3.3 Rollup Reports 523

5.8 VMware ESX Server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5295.8.1 Topology Viewer for VMware Environment . . . . . . . . . . . . . . . . . . . 5315.8.2 Reports for VMware Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 535

5.9 Troubleshooting and housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5535.9.1 Determining the version of Agent Manager. . . . . . . . . . . . . . . . . . . 5535.9.2 The Agent Manager toolkit for administrators . . . . . . . . . . . . . . . . . 5545.9.3 Reregistering a Common agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 5565.9.4 Connecting a Common agent to a new Agent Manager . . . . . . . . . 5575.9.5 Using repocopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

Appendix A. Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565User IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

Server information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566Worksheet for user IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 567User IDs and passwords for key files and installation. . . . . . . . . . . . . . . . 568

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571TotalStorage Productivity Center documentation. . . . . . . . . . . . . . . . . . . . . . 571Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

Contents vii

viii Deployment Guide Series: IBM TotalStorage Productivity Center for Data

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2009. All rights reserved. ix

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

AIX 5L™AIX®BladeCenter®DB2 Universal Database™DB2®DS4000®DS6000™DS8000®Enterprise Storage Server®FlashCopy®

GPFS™HACMP™IBM®NetView®POWER5™POWER6™POWER®Redbooks®Redbooks (logo) ®System i®

System p®System Storage™System x®System z®Tivoli Enterprise Console®Tivoli®TotalStorage®WebSphere®z/OS®

The following terms are trademarks of other companies:

Network Appliance, WAFL, FlexVol, Data ONTAP, NetApp, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and other countries.

Novell, SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and other countries.

Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its affiliates.

QLogic, and the QLogic logo are registered trademarks of QLogic Corporation. SANblade is a registered trademark in the United States.

Red Hat, and the Shadowman logo are trademarks or registered trademarks of Red Hat, Inc. in the U.S. and other countries.

VMware, the VMware "boxes" logo and design are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Java, JDBC, JRE, JVM, Solaris, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Active Directory, Internet Explorer, Microsoft, MS, SQL Server, Windows NT, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

x Deployment Guide Series: IBM TotalStorage Productivity Center for Data

http://www.ibm.com/legal/copytrade.shtml

Preface

IBM® TotalStorage® Productivity Center for Data (Data Manager) is a comprehensive file and capacity management solution for heterogeneous storage environments. It includes enterprise-wide reporting and monitoring, policy-based management, and automated capacity provisioning for Direct Attached Storage (DAS), Network Attached Storage (NAS), and storage area network (SAN) environments. Data Manager, Data Manager for Databases, and Data Manager for Chargeback let you improve storage utilization, plan for future capacity, and ensure availability by providing storage on demand for filesystems.

This IBM Redbooks® publication is intended for administrators and users who are installing and using IBM TotalStorage Productivity Center for Data. It provides an overview of the product and its functions. It describes the hardware and software environment required and provides a step-by-step installation procedure. Customization and usage information is also provided. The reader needs to have a basic understanding of storage concepts, network topologies, communication protocols, and a basic understanding of the IBM TotalStorage Productivity Center product.

This book focuses on the TotalStorage Productivity Center for Data component as an integral part of the TotalStorage Productivity Center product. It is not a replacement for the existing IBM Redbooks publications, or product manuals, that detail the implementation and configuration of the individual products that make up the IBM TotalStorage Productivity Center. We refer to those books as appropriate throughout this book.

The team that wrote this IBM Redbooks publicationThis IBM Redbooks publication was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center. The team that wrote this book is shown in Figure 1 on page xii.

Mary Lovelace is a Consulting IT specialist at the International Technical Support Organization. She has more than 20 years of experience with IBM in large systems, storage and Storage Networking product education, system engineering and consultancy, and systems support. She has written many IBM Redbooks publications about TotalStorage Productivity Center and z/OS® storage products.

© Copyright IBM Corp. 2009. All rights reserved. xi

Alejandro Berardinelli is an IT Specialist with IBM Uruguay. Since joining IBM, Alejandro has been providing z/OS software support. His primary focus is on Tivoli® Storage Manager deployments for multiple platforms, including AIX®, Linux®, Windows®, and z/OS. He also performs IBM storage implementations involving disk, tape subsystems, and switches. Alejandro is working on a Computer Engineer degree at UDELAR.

Kamalakkannan Jayaraman is an IT Specialist working with IBM India Software Labs. His areas of expertise include multivendor disk, SAN, tape solves, UNIX®, and Windows operating systems. His current job includes designing and implementing storage solutions. He is a Brocade Certified Fabric Professional, a SNIA Certified Professional, and an HP Certified Professional.

Nidhi Khator is an Associate System Engineer working with IBM Global Business Services. Her areas of expertise includes AIX, SUSE® Linux, Red Hat® Enterprise Linux, VMWare ESX Server, and IBM Storage Administration. Her current job role is to provide end-to-end support to data centers hosting IBM System p®, IBM System x®, and IBM BladeCenter® servers and IBM System Storage™ DS4800 and DS4500 servers. She is an IBM certified System p administrator and System p Enterprise Technical Support for AIX 5L™ V5.3.

Figure 1 Alejandro, Mary, Nidhi, and Kamalakkannan

The authors of the previous version of this book are Sanver Ceylan, Hartmut Harder, and Murat Hakan Yesilmen.

xii Deployment Guide Series: IBM TotalStorage Productivity Center for Data

Thanks to the following people for their contributions to this project:

Special thanks to Vasfi Gucer for his continuous support.

Werner EggliStefan LeinMarcus StandauTotalStorage Productivity Center IBM Redbooks publication authors

Elizabeth Purzer, Worldwide Tivoli Channels Program ManagerJoe Gatti, Tivoli Storage SWAT TeamDoug Dunham, former Tivoli Storage SWAT TeamIBM Software Group, Tivoli

Jason Bamford, EMEA NR - Storage Software Specialist

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbooks publication dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will team with IBM technical professionals, IBM Business Partners, and clients.

Your efforts will help increase product acceptance and client satisfaction. As a bonus, you will develop a network of contacts in the IBM development labs and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcomeYour comments are important to us!

We want our IBM Redbooks publications to be as helpful as possible. Send us your comments about this or other IBM Redbooks publications in one of the following ways:

� Use the online Contact us review IBM Redbooks publications form found at:

ibm.com/redbooks

Preface xiii

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html



� Send your comments in an e-mail to:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400

xiv Deployment Guide Series: IBM TotalStorage Productivity Center for Data

http://www.redbooks.ibm.com/contacts.html

Summary of changes

This section describes the technical changes made in this edition of the book and in previous editions. This edition might also include minor corrections and editorial changes that are not identified.

Summary of Changesfor SG24-7140-03for Deployment Guide Series: IBM TotalStorage Productivity Center for Dataas created or updated on June 25, 2009.

June 2009, Third Edition

This revision reflects the addition, deletion, or modification of new and changed information, as described below.

New information� TotalStorage Productivity Center for Data V3.3 product enhancements

documented

� How to maintain your TPC for Data repository data and agents

© Copyright IBM Corp. 2009. All rights reserved. xv

xvi Deployment Guide Series: IBM TotalStorage Productivity Center for Data

Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data

In this chapter, we provide an overview of TotalStorage Productivity Center for Data. We include a high-level technical introduction to IBM TotalStorage Productivity Center, its architecture, and base concepts. We discuss the following topics:

� What is IBM TotalStorage Productivity Center� TotalStorage Productivity Center for Data overview� Features� Architecture� Supported levels for Version 3 Release 3

1

© Copyright IBM Corp. 2009. All rights reserved. 1

1.1 What is IBM TotalStorage Productivity CenterIBM TotalStorage Productivity Center is an integrated set of software components that provides end-to-end storage management, from the host and application to the target storage device, in a heterogeneous platform environment. This software offering provides disk and tape library configuration and management, performance management, storage area network (SAN) fabric management and configuration, and host-centered usage reporting and monitoring from the perspective of the database application or filesystem. TotalStorage Productivity Center:

� Simplifies the management of storage infrastructures

� Manages, configures, and provisions SAN-attached storage

� Monitors and tracks the performance of SAN-attached devices

� Monitors, manages, and controls (through zones) SAN fabric components

� Manages the capacity utilization and availability of filesystems and databases

TotalStorage Productivity Center V3.3 is an integrated storage infrastructure management solution that simplifies, automates, and optimizes the management of storage devices, storage networks, and capacity utilization of filesystems and databases. TotalStorage Productivity Center V3.3 helps you:

� Manage the capacity utilization of filesystems and databases

� Automate filesystem capacity provisioning

� Perform device configuration and management of multiple devices from a single user interface

� Tune and proactively manage the performance of storage devices on the SAN

� Manage, monitor, and control your SAN fabric

TotalStorage Productivity Center V3.3 provides a single management platform that allows you to centralize how you manage your storage infrastructure. By providing an integrated suite with management modules focused on various aspects of the storage infrastructure, TotalStorage Productivity Center delivers the capability to use role-based administration, single sign-on, and a single management server and repository. The central console provides a centralized place to monitor, plan, configure, report, and perform problem determination on the SAN fabric, storage arrays, and storage capacity.

2 Deployment Guide Series: IBM TotalStorage Productivity Center for Data

1.1.1 TotalStorage Productivity Center structure In this section, we look at the TotalStorage Productivity Center structure from the logical and physical views.

Logical structureThe logical structure of TotalStorage Productivity Center is composed of three layers, as shown in Figure 1-1 on page 4.

� The infrastructure layer consists of basic functions, such as messaging, scheduling, logging, device discovery, and a consolidated database that is shared by all components of TotalStorage Productivity to ensure consistent operation and performance.

� The application layer consists of core TotalStorage Productivity Center management functions, based on the infrastructure implementation, that provide various disciplines of storage or data management. These application components are most often associated with the product components that make up the product suite, such as fabric management, disk management, replication management, and data management.

� The interface layer presents integration points for the products that make up the suite. The integrated graphical user interface (GUI) brings together product and component functions into a single representation that seamlessly interacts with the components to centralize the tasks for planning, monitoring, configuring, reporting, viewing topology, and problem determination.

Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 3

Figure 1-1 TotalStorage Productivity Center logical structure

Physical structureTotalStorage Productivity Center is comprised of a data component, which is TotalStorage Productivity Center for Data, a fabric component, which is TotalStorage Productivity Center for Fabric, a disk component, which is TotalStorage Productivity Center for Disk and a replication component, which is TotalStorage Productivity Center for Replication. TotalStorage Productivity Center includes a centralized suite installer, and TotalStorage Productivity Center for Data and TotalStorage Productivity Center for Fabric share a Common agent to manage the fabric as well as capacity utilization of filesystems and databases.

TotalStorage Productivity Center for DataTotalStorage Productivity Center for Data, the topic of this book, can provide over 300 enterprise-wide reports, monitoring and alerts, policy-based action, and filesystem capacity automation in an heterogeneous environment.

TotalStorage Productivity Center for Fabric TotalStorage Productivity Center for Fabric can provide automated device discovery, topology rendering, error detection fault isolation, SAN error predictor, zone control, real-time monitoring and alerts, and event management for heterogeneous enterprise SAN environments.


TotalStorage Productivity Center for Disk TotalStorage Productivity Center for Disk brings in the Performance Manager feature and can enable device configuration and management of supported SAN-attached devices from a single console.

TotalStorage Productivity Center for ReplicationThe basic functions of TotalStorage Productivity Center for Replication are designed to provide management of the advanced copy services for the IBM System Storage DS8000®, IBM TotalStorage Enterprise Storage Server® (ESS) Model 800, IBM System Storage DS6000™, and the IBM System Storage SAN Volume Controller (SVC). The advanced copy services include IBM FlashCopy®, Metro Mirror, and Global Mirror capabilities.

TotalStorage Productivity Center for Replication focuses on automating administration and configuration of the advanced copy services, operational control (starting, suspending, and resuming) of copy services tasks, and monitoring and managing the copy services sessions.

Advanced disaster recovery functions are also supported with failover/failback (planned and unplanned) from a primary site to a disaster recovery site.


Figure 1-2 shows the TotalStorage Productivity Center physical structure.

Figure 1-2 TotalStorage Productivity Center structure

The Data server is the control point for product scheduling functions, configuration, event information, reporting, and GUI support. It coordinates communication with agents and data collection from agents that scan filesystems and databases to gather storage demographics and populate the database with results. Automated actions can be defined to perform filesystem extension, data deletion, and Tivoli Storage Manager backup, archiving, or event reporting when defined thresholds are encountered. The Data server is the primary contact point for GUI user interface functions. It also includes functions that schedule data collection and discovery for the Device server.

The Device server component discovers, gathers information from, analyzes the performance of, and controls storage subsystems and SAN fabrics. It coordinates communication with agents and data collection from agents that scan SAN fabrics.

The single database instance serves as the repository for all TotalStorage Productivity Center components.


The Data agents and Fabric agents gather host, application, and SAN fabric information and send this information to the Data server or Device server.

The graphical user interface (GUI) allows you to enter information or receive information for all TotalStorage Productivity Center components.

The command-line interface (CLI) allows you to issue commands for major TotalStorage Productivity Center functions.

1.2 TotalStorage Productivity Center for Data overviewTotalStorage Productivity Center for Data is designed to provide a comprehensive storage resource management (SRM) solution for heterogeneous storage environments across the enterprise. It includes enterprise-wide reporting and monitoring, policy-based management, and automated capacity provisioning for direct-attached storage (DAS), network-attached storage (NAS), and storage area network (SAN) environments. IBM TotalStorage Productivity Center for Data enables administrators to identify, manage, control, and predict storage usage. It also provides filesystem and database management and reporting on storage capacity and growth.

TotalStorage Productivity Center for Data provides over 300 enterprise-wide reports, monitoring, and alerts, policy-based action, and filesystem capacity automation in the heterogeneous environment. It allows you to create customized reports as well. The standardized reports provide information about filesystems, databases, and storage infrastructure. These reports provide the storage administrator information about:

� Assets� Availability � Capacity � Usage � Usage violation� Backup� Reports for files based on criteria such as data type, size, and last referenced

TotalStorage Productivity Center for Data helps improve capacity utilization of filesystems and databases and helps add intelligent data protection and retention practices.

TotalStorage Productivity Center for Data performs the following functions:

� Discovers and monitors disks, partitions, shared directories, and servers

� Monitors and reports on capacity and utilization across platforms to help you to identify trends and prevent problems


� Monitors storage assets that are associated with enterprise-wide databases and issues notifications of potential problems

� Provides a wide variety of standardized reports about filesystems, databases, and storage infrastructure to track usage and availability

� Provides file analysis across platforms to help you to characterize your data and, in turn, identify and reclaim space used by non-essential files

� Provides policy-based management and automated capacity provisioning for filesystems when user-defined thresholds are reached or a condition is met

� Generates invoices that charge back for storage usage on a departmental, group, or user level

These functions that are available with Data Manager are designed to help decrease storage costs by:

� Improving storage utilization

� Enabling intelligent capacity planning

� Supporting application availability through computer uptime reporting and application database monitoring

� Provide automation for invoking backups, archiving, scripts, publishing reports to Web servers, and so on

The architecture of TotalStorage Productivity Center for Data enables system administrators to see all of the storage assets, including direct-attached storage and network-attached storage. This comprehensive view of the entire storage map allows the administrators to manage much larger environments and also to get the information about utilization and usage that is typically required in large environments.

The information collected by TotalStorage Productivity Center for Data can help you make intelligent decisions about optimizing the utilization of your open system environments. The data collected by TotalStorage Productivity Center for Data helps you to understand what is happening to the data that resides on your servers. The collected data includes views illustrating when files are created, accessed, and modified, and by which group or user. This type of information enables system administrators to map the actual storage resource to the consumers of that resource. The ability to map storage consumption to storage hardware has become increasingly important as the size of open systems’ environments has increased. In addition to understanding the current consumption and usage of data within the enterprise, TotalStorage Productivity Center for Data keeps track of this information over time. Not only does this historical view of storage consumption and utilization allow you to see usage trends over time, it also enables the system administrator to see a projected use of storage into the future. This capability allows the system administrator to plan


the purchase of additional capacity in a planned, proactive manner rather than just react to your system running out of space.

The major components of TotalStorage Productivity Center for Data are:

� Data Manager

The Data Manager controls the discovery, monitoring, reporting, and alert functions. Data Manager:

– Receives information from the agents and stores that information in the central repository and issues commands to agents for jobs

– Receives requests from clients for information and retrieves the requested information from the central data repository

Data Manager can help you identify, evaluate, control, and predict your enterprise storage management assets. Because it is policy-based, it can detect potential problems and automatically make adjustments based on the policies and actions that have been created. For example, it can notify you when your system is running out of disk space or warn you of storage hardware failure. By alerting you to these and other issues related to your stored data, it gives you an opportunity to prevent unnecessary system and application downtime.

� Data agents on managed systems

An agent resides on each managed system. Each agent performs the following functions:

– Runs probes and scans

– Collects storage-related information about the volumes or filesystems that are accessible to the managed systems

– Forwards information to the manager to be stored in the database repository

� Web server

The optional Web server permits remote Web access to the server.

� Clients

Clients communicate directly to Data Manager to perform administration, monitoring, and reporting. A client can be a locally installed interface to Data Manager, or it can use the Web server to access the user interface through a Web browser.


1.3 FeaturesIn this section, we describe the significant features of TotalStorage Productivity Center for Data.

Policy-based managementTotalStorage Productivity Center for Data can enable you to define and enforce storage policies through the use of user-defined alerts, quotas, and constraints. TotalStorage Productivity Center for Data notifies the user by e-mail, pager, SMS, the event log, or a systems management console for events, such as exceeding a quota or violating a constraint.

Your objective is not only to identify problems, but you need a way to correct the problems as well. TotalStorage Productivity Center for Data can provide automated solutions through event management. For example, if TotalStorage Productivity Center for Data discovers data that has not been accessed in more than a year, it can be enabled to trigger Tivoli Storage Manager to back up or archive files.

This feature allows you to effectively manage your storage. Benefits include the consistent deployment of storage resource management policies across platforms, automated scheduled reporting, and automated filesystem extension.

Automatic filesystem extensionThrough monitoring, TotalStorage Productivity Center for Data detects when a filesystem has exceeded a user-defined threshold and automatically extends the filesystem to prevent an out of space condition. When used in conjunction with an ESS, a logical unit number (LUN) is created and provisioned to the filesystem automatically.

A probe runs on agents and sends filesystem statistics to the server. The server compares the current filesystem state against the target policy and invokes provisioning and an extension as necessary.

Tivoli Storage Manager integrationWith this feature, TotalStorage Productivity Center for Data can automatically invoke Tivoli Storage Manager to archive and delete files. This can free up space in a filesystem and can allow you to more effectively manage storage utilization. For example, a policy can be created to archive all files over 365 days old to tape using IBM Tivoli Storage Manager and then delete the files to free up the disk space.


Subsystem reportingTotalStorage Productivity Center for Data gathers and reports on disk subsystems. The information includes physical characteristics, such as the drive’s manufacturer, model, serial number, capacity, and rotational speed. Also, the information includes how that drive’s storage is allocated to logical volumes, snapshot copy volumes, and free space. This feature allows users to perform the following tasks (subject to the vendor’s implementation of Storage Management Initiative Specification (SMIS)):

� Display the physical disks behind what the host sees as a disk drive� Show the allocated and free capacity of subsystems in the network� List subsystem volumes that have been allocated but are not in use� Show which hosts have access to a given subsystem volume� Show which hosts have access to a given disk drive (within the subsystem)� Show which subsystem volumes (and disks) a host can access� Obtain SAN Volume Controller (SVC) reporting

Enterprise rollup reportingTotalStorage Productivity Center for Data can enable a storage administrator to use a single interface to generate reports based on data collected by multiple TotalStorage Productivity Center servers. As a storage administrator, you can perform the following actions:

� Combine reports for multiple TotalStorage Productivity Center servers into an enterprise-wide report, which enables you to view results for your entire environment.

� Partition a large number of agents across multiple Data servers. This feature alleviates performance issues when running aggregation reports and scan jobs for multiple agents on one Data server.

To provide enterprise-wide reporting, the monitored environment has to have at least one TotalStorage Productivity Center Standard Edition server configured as a master TPC Server. This server is configured to collect rollup information from subordinates. The master server communicates with the subordinate servers using the Device server application programming interface (API).

Topology ViewerThe IBM TotalStorage Productivity Center Topology Viewer is designed to provide an extended graphical topology representation of the physical and logical resources (for example, computers, fabrics, and storage subsystems) in your storage environment. In addition, the Topology Viewer depicts the relationships among resources (for example, the disks comprising a particular storage subsystem). Detailed, tabular information (for example, attributes of a disk) is also provided.


The overall goal of the Topology Viewer is to provide a central location to view a storage environment, quickly monitor and troubleshoot problems, and gain access to additional tasks and functions within the IBM TotalStorage Productivity Center graphical user interface (GUI).

The Topology Viewer uses the IBM TotalStorage Productivity Center database as the central repository for all of the data that it displays. It retrieves the data in user-defined intervals from the database and updates, as necessary, the displayed information automatically.

NAS supportTotalStorage Productivity Center for Data can enable storage administrators to monitor, report on, and manage network-attached storage (NAS) resources. TotalStorage Productivity Center for Data is designed to provide a universal view of direct-attached and network-attached storage, from a filesystem or application perspective. For Network Appliance™ files, TotalStorage Productivity Center for Data monitors, reports on, and manages physical disk information, such as the total disk capacity and disk usage information. By providing this information as part of a universal view of enterprise storage, storage administrators can manage storage from a logical (filesystem) perspective as well as a physical (disk) perspective. Administrators can also view information for a single filer, a group of filers, a user or group of users, or all filers enterprise-wide, enabling them to manage all enterprise storage resources from a single Web-based interface, to help them reduce costs and increase availability by pinpointing and solving problems more effectively.

VMware supportThe VMware® ESX Server is a hypervisor product, which can host multiple virtual machines that run independently of each other while sharing hardware resources. VMware allows a single physical computer system to be divided into logical virtual machines running various operating systems. To the applications running inside the virtual machine (VM), it is a computer system with a unique IP address and access to storage that is virtualized by the hosting system, which is also known as the hypervisor.

The VMware VirtualCenter is the management application that is the central entry point for the management and monitoring of multiple ESX Servers in a data center. To utilize the improved VMware support, two data sources are required: A VMware ESX Server and the VMware Virtual Infrastructure data sources. The new VMware VI Data Source interfaces with the ESX Server, and the TPC Data agent is installed on each virtual machine that you plan to monitor. For more details about using VMware ESX Server, refer to 5.8, “VMware ESX Server support” on page 529.


Advanced provisioningTotalStorage Productivity Center and Tivoli Provisioning Manager Workflow automation can reduce provisioning time from hours to minutes and significantly simplify the task of provisioning new storage capacity. This automation is especially valuable when adding storage provisioning to existing automated server provisioning tasks, such as deploying operating systems, software, and network resources.

Comprehensive reportingWith a wide variety of predefined reports, from summaries to detailed reports on storage assets, you can optimize storage, minimize downtime, and streamline storage management.

Monitoring and alertsTotalStorage Productivity Center for Data monitors storage assets and discovers newly added storage resources on your network with centralized administration from a Single graphical user interface. TotalStorage Productivity Center for Data allows you to set thresholds and alerts so that you can be notified by e-mail, SMS, a Simple Network Management Protocol (SNMP) trap, or a UNIX or Microsoft® Windows Event log when certain conditions occur.

Database supportTotalStorage Productivity Center for Data manages the storage assets within your database application allowing you to identify the fastest growing databases, spot potential trouble areas, reclaim unused space, and predict future storage needs.

Chargeback supportTotalStorage Productivity Center for Data offers an end-to-end system for invoicing your cost centers based on their storage usage. TotalStorage Productivity Center for Data makes your data owners aware of and accountable for their data usage, helping to keep storage costs distributed accurately across an organization.


1.3.1 What is new in TotalStorage Productivity Center V3.3.2TotalStorage Productivity Center V3.3.2 adds the following new features, functions, and enhancements.

Internet Protocol Version 6IBM TotalStorage Productivity Center now supports Internet Protocol Version 6 (IPv6). This expands the IP address from 32 bits to 128 bits. There are special considerations and rules for supporting IPv6 in TotalStorage Productivity Center. For more information, refer to 2.2.4, “IPv6 considerations” on page 42.

Virtual I/O ServerTotalStorage Productivity Center supports the installation of Data agents and Fabric agents on the Virtual I/O Server for AIX. You must use the padmin user ID to install and configure the agents. For information about planning for installing the agents on the Virtual I/O Server, refer to 2.8.3, “Virtual I/O Server agent installation” on page 65.

AIX V6.1TotalStorage Productivity Center now supports AIX V6.1 for the TotalStorage Productivity Center server and agents. To run with AIX V6.1, you must have DB2® V9.1 with Fix Pack 4 or DB2 V8.1 with Fix Pack 16 installed. For more details about AIX installation, refer to 3.5, “AIX installation” on page 215.

TotalStorage Productivity Center universal agentA universal agent for TotalStorage Productivity Center is available to report TotalStorage Productivity Center asset information to IBM Tivoli Monitoring. This data is available for display in the Tivoli Enterprise Portal for reporting, charting, and establishing situations in Tivoli Monitoring.

The instructions for retrieving the TotalStorage Productivity Center universal agent included with V3.3.1 has been changed. You no longer retrieve the universal agent from Open Process Automation Library (OPAL).

The universal agent is located in the following TotalStorage Productivity Center directory:

� For Windows: <TPC_install_dir>\tool\TPCUA.zip> � For UNIX and Linux: /<opt or usr>/tool/TPCUA.tar

The zip or tar file contains a readme file that describes how to install and configure the universal agent.


For more information about IBM Tivoli Monitoring and Tivoli Enterprise Portal, go to the following address:

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc==/com.ibm.itm.doc/toc,.xml

Hitachi Data Systems TagmaStoreTotalStorage Productivity Center now supports the Hitachi Data Systems TagmaStore Common Information Model (CIM) agent V5.8. This version of the CIM Agent supports only the Array Profile and not the Virtualizer Profile. However, IBM TotalStorage Productivity Center supports the TagmaStore as a Storage Virtualizer. IBM TotalStorage Productivity Center can display information for virtual disks and local disks.

VMware Virtual InfrastructureVMware ESX Server support was provided in TotalStorage Productivity Center V3.3.0. With TotalStorage Productivity Center V3.3.2, additional support has been added:

� TotalStorage Productivity Center supports VMware ESX Server V3.5, VMware ESX Server V3.5 3i, and VMware VirtualCenter V2.5. The ESX Server V3.5 3i is the hardware-integrated hypervisor. Reports now show the logical unit number (LUN) correlation.

� TotalStorage Productivity Center also supports ESX Server V3.0 and VirtualCenter V2.0, but does not support the LUN correlation for these releases.

Launch-in-context featureThe launch-in-context feature can be used to download the latest version of the TotalStorage Productivity Center graphical user interface (GUI) on the local workstation using Java™ Web Start. The TotalStorage Productivity Center GUI must have been previously installed on the local workstation. The launch-in-context feature downloads the latest version of the GUI on the local workstation if an older version has been downloaded, or if the IBM TotalStorage Productivity Center GUI has not been previously downloaded. If the latest version exists on the local workstation at the Java Web Start download location, the TotalStorage Productivity Center GUI is not downloaded.

The launch-in-context feature can be run in the following ways:

1. From a URL with Java Web Start. You can remotely download and launch the TotalStorage Productivity Center GUI, using the launch-in-context feature, and perform a certain number of actions on a remote system.




2. From the command line with Windows, Linux, or UNIX. (The IBM TotalStorage Productivity Center GUI must have been previously installed on the local workstation if it is to be launched through the command line.)

3. From the Windows Start menu.

4. From the Tivoli Enterprise Portal GUI.

The additional TPC V3.3.2 functions that can be launched on the remote system (in addition to the functions supported in the previous release) are:

1. Create Volume

2. Create VDisk

3. Launch SAN Planner

4. Launch Wasted Space report

High-Availability Cluster Multi-Processing support on AIXTotalStorage Productivity Center supports Data agents and Fabric agents installed on High-Availability Cluster Multi-Processing (HACMP™) nodes. You will be able to monitor the cluster resource groups. You can probe the HACMP cluster to get cluster reports and produce alerts when changes occur in the HACMP cluster.

The HACMP software supports both the non-concurrent and concurrent cluster resource groups. TotalStorage Productivity Center does not support concurrent cluster resource groups

The installation procedure for installing the agents is the same as installing the agents on an AIX server (refer to 4.2, “Local installation of Data and Fabric agents” on page 289).

DS8000 space-efficient volumesTotalStorage Productivity Center supports the DS8000 space-efficient volumes. Using space-efficient volumes, you can copy only those blocks (which have been written to) to a target.

Information about space-efficient volumes and their relationship to extent pools is collected. Information about virtual pools is collected but does not persist in the database. You can identify space-efficient volumes in the topology viewer and in reports. You cannot use Disk Manager to create or delete space-efficient volumes. When you use space-efficient volumes, you cannot see the real allocated space, but can see the consumable space, so you cannot create a report using summarized volume capacity.


SMI-S supportTotalStorage Productivity Center now supports the SMI-S as the single standard interface for managing SANs. You no longer need the in-band agents for zone discovery and zone control operations. TotalStorage Productivity Center uses the SMI-S Fabric Profile and related SubProfiles for inventory collection of SAN topology and zoning, for active configuration of zoning, and for fabric and switch alerts for the switch vendors.

This support applies to Brocade and McDATA switches for the following:

� Topology discovery

� Zoning discovery

� Zone control of zone sets and zones

� Alerts from fabric and switch events

� Launching switch or fabric element managers

The earlier interfaces (SNMP and GS-3) will still be necessary for QLogic® and Cisco switches and SANs.

Refer to the following address for the list of supported SAN switches.

http://www-01.ibm.com/support/docview.wss?rs=1134&uid=swg21265379

Automount maps in Sun SolarisYou can skip automount maps (automaps) for a discovery job on Sun™ Solaris™. To skip automount maps, specify the skipAutoFS=1 parameter in the server section of the TPCD.config file.

TotalStorage Productivity Center Assistant not supportedTotalStorage Productivity Center Assistant is no longer available as a separate tool. The links that were previously provided by this tool have been merged into the TotalStorage Productivity Center user interface under the Help menu. This includes links to the TotalStorage Productivity Center Information Center, supported products matrixes, and product demonstration Web pages.

1.4 ArchitectureTotalStorage Productivity Center for Data has four major components: the server, scheduler, GUI, repository, and agent. There is also a Common Information Model Object Manager (CIMOM) component that is used for collecting data from storage subsystems, such as the IBM DS8000, DS6800, ESS, SVC, and DS4000® servers.


http://www-01.ibm.com/support/docview.wss?rs=1134&uid=swg21265379

Figure 1-3 illustrates the architectural overview for TotalStorage Productivity Center for Data.

Figure 1-3 TotalStorage Productivity Center for Data architecture

The left section of Figure 1-3 shows various types of workstations that are running user interface (UI) components for accessing TotalStorage Productivity Center server. We have two types of clients available: a Web-based client and a regular “fat” Java client.

The Managing Servers section in the middle of Figure 1-3 illustrates TotalStorage Productivity Center servers, which are necessary from an architectural point of view. The Web server runs most often as an integral part of your TotalStorage Productivity Center Server, but it can be a separate server as well.

All user requests are sent by the UI to the TotalStorage Productivity Center server. In the next step, the server gets the appropriate data from the repository and returns it to the UI, allowing the user to create and display reports. Note that the timeliness of the data displayed is dependent on the contents of the database.


The Managed Resources section on the right side of Figure 1-3 on page 18 illustrates machines that are running the TotalStorage Productivity Center for Data agent component. These machines are the systems from which the TotalStorage Productivity Center server gathers its information, which needs to be done on a regular and scheduled basis in order to keep the information in the repository as current as possible.

The architectural diagram in Figure 1-3 on page 18 provides a logical overview of the main conceptual elements and relationships in the architecture, components, connections, users, and external systems. The diagram also shows the various methods that are used to collect information from multiple systems to give an administrator the necessary views of the environment, for example:

� Software clients (agents)

� Standard interfaces and protocols (for example, Simple Network Management Protocol)

� Common Information Model Object Manager (CIMOM agent)

� Repository

� Agent Manager with its registry repository

1.4.1 Data flowFigure 1-4 on page 20 represents sample data flow between IBM TotalStorage Productivity Center and major components, such as agents, Data Manager Web UI, and CIMOMs. Figure 1-4 on page 20 also shows the interaction point with IBM TotalStorage Provisioning Manager.

A key strength of the TotalStorage Productivity Center solution is that the TotalStorage Productivity Center for Data can be integrated as one solution with TotalStorage Productivity Center for Disk and TotalStorage Productivity Center for Fabric sharing a common interface. These applications share the same architectural elements, such as Tivoli Common agent, which is installed on the appropriate servers, and the Agent Manager, which authenticates and secures connections between server components, such as Data Manager and the agents.

IBM Tivoli Provisioning Manager is an important application that supports the IBM On Demand Business vision. Pivotal to delivering the automation and provisioning strategies of this vision are products, such as IBM TotalStorage Productivity Center. The IBM TotalStorage Productivity Center with Advanced Provisioning offering is designed to allow assisted capacity provisioning capabilities through automated workflows. Storage provisioning using IBM TotalStorage Productivity Center with Advanced Provisioning helps you save time and avoid human error by automating the many steps that are involved in


allocating storage to an application or user. Provisioning automates the way IT resources are made available. IBM Tivoli Provisioning Manager helps clients significantly reduce the time that it takes to accomplish complex IT tasks, while eliminating the risk of human error by automating complex IT processes using best practices.

Figure 1-4 Data flow

1.4.2 Schema of interactionsOn Figure 1-5 on page 23, we show the high-level architecture and agent interaction in the IBM TotalStorage Productivity Center for Data product. We show the protocols that are used to monitor and manage the storage subsystem.

The three layers in the graphic in Figure 1-5 on page 23 represent the various component areas, such as the server, the agent, and the proxy agents. The scheduler service is running on the server component.


1.4.3 Data Manager server The server is the center of Data Manager’s architecture and directs all of the activities related to the monitoring performed on the monitored agent computers and the reporting performed on the Client GUI computers. The server interacts with the Enterprise Repository, Job Scheduler, agents, and Agent Manager (used for authorization and authentication of agents).

Data Manager receives information from the agents and then inserts that information in the repository. The repository is where all of your storage information and usage statistics are stored. All agent and user interface access to the central repository is done through a series of calls and requests made to the server.

The Data Manager server consists of two components: the Enterprise Repository and the Job Scheduler.

Enterprise Repository The Data Manager server monitors your environment to accumulate information about its storage assets and their usage over time. It records this information in the centralized Enterprise Repository. The repository is organized into a series of relational database tables and is accessed by Data Manager using Java Database Connectivity (JDBC™). Java Database Connectivity is a standard SQL database access interface that provides uniform access to a wide range of relational databases. Data Manager currently supports only DB2 UDB.

Job Scheduler Data Manager deploys monitoring activities using an embedded job scheduler. This job scheduler controls when to run discovery, ping, probe, scan, and quota checking jobs, as well as other functions, such as running scripts and creating reports. It provides robust scheduling functionality and the flexibility to specify exactly when to run monitoring jobs. You can schedule jobs to run immediately or to run repeatedly on a specified schedule. You define and save the scheduling information as part of the monitoring specification. The monitoring job then runs on that schedule until the job is either changed, deleted, or disabled.

1.4.4 User interfaceThe user interface (UI) enables users to request information and then generate and display reports based on that information.


The Client UI Component of Data Manager provides the user interface for:

� Monitoring your storage � Defining and receiving alerts on storage events � Generating and viewing reports

As Data Manager monitors your storage across your enterprise, it accumulates a repository of knowledge about your storage assets and how they are used. You can use the reports that are provided in the user interface view and analyze that repository of information from multiple perspectives to gain insight into the use of storage across your enterprise. See 5.4, “Reporting” on page 450 for more information about reports.

AgentsAgents collect statistics about your storage and send that information to the centralized Data Manager component. The agent is installed on each machine containing storage that needs to be monitored. Data Manager uses a Common Information Model Object Manager (CIMOM) agent to gather information about storage subsystem controllers. The Agent component runs in the background and deploys monitoring jobs, such as pings, probes, and scans. It interacts with the Job Scheduler and deploys monitoring jobs according to the schedules that you have defined, which allows an agent to:

� Detect low-level problems, such as defects in the hardware containing the storage information

� Keep track of information, such as the uptime and downtime of the machine on which it is running

� Return information to the server from the scans and probes

Agents receive jobs to run from a server’s scheduling service and then contact the server for the job definition. When the agent receives the job definition successfully, no further communication to the server is required until the job completes.

� For NetWare servers: Install and license an agent on a machine that:

– Is running a supported Windows platform. To use Data Manager for retrieving storage information from the servers and volumes within Novell® Directory Services (NDS) trees, you must install its agent on a Windows machines where a Novell NetWare client is already located. Data Manager gathers detailed storage information about NetWare servers and volumes using native NetWare calls from these Windows machines.

Note: All database access is done using the server component to maximize performance and to eliminate the need to install database connectivity software on your agent and UI machines.


– Has an installed NetWare Client.

– Has access to the Novell NetWare servers and volumes within your environment.

� For NAS support, install and license an agent on Windows or UNIX machines from which the NAS filers that you want to scan are visible. For example, install agents to Windows machines that can access your NAS filers, and install agents on UNIX/Linux machines that have imports for the filesystems within the NAS filers.

See 4.9.1, “Manual NAS/NetWare server entry” on page 345 for more information.

For Microsoft Cluster Server (MSCS) support, install and license an agent on every cluster node machine.

Figure 1-5 High-level architecture

DataRepository

StorageHost

CM Agent

CIM/OM

EnterpriseStorage Server

LUNFile and

PrintServer

ApplicationServer

Proxy Agents

Agents

IBM Storage Resource Manager Server

JDBC

TCP/IP

SLP

SNMP, NFS, CIFS, NCP

Disk

Server

Scheduler

TCP/IP


Agent ManagerAgent Manager provides authentication and authorization using X.509 certificates and the Secure Sockets Layer (SSL) protocol. Agent Manager processes queries about its registry of configuration information about the agents and management applications.

Data Manager and agents must register with the Agent Manager before they can use its services to communicate with each other. Agent Manager is the first component that you install in your environment; you cannot register Data Manager server or any agents without it. Registration is password-protected and requires separate passwords for agent registration and Resource Manager registration. The registry is a database that contains the current configurations of all known agents and resource managers. The registry is in a DB2 database.

The Agent Manager also provides an Agent Recovery Service, which is a network service for error logging for agents that cannot communicate with other Agent Manager services. Agents use an unsecured HTTP connection to communicate with the Agent Recovery Service on the port number. Because the connection is unsecured, an agent can always communicate with the Agent Recovery Service, even if the agent is incorrectly configured or has expired or revoked certificates. The Agent Recovery Service is a WebSphere® servlet container. Agents locate the Agent Recovery Service using the unqualified host name TivoliAgentRecovery and port 80. The Agent Recovery Service runs on the Agent Manager server. There must be an entry on your Domain Name System (DNS) server that maps the host name TivoliAgentRecovery to the computer system where you installed the Agent Manager.

1.4.5 Integration points with TEC and IBM Tivoli Storage ManagerIn this section, we describe TotalStorageProductivity Center for Data integration points with IBM Tivoli Enterprise Console® (TEC) and IBM Tivoli Storage Manager. The integration with IBM Tivoli Enterprise Console is done through the alert notification facility.

Alert notificationThe main purpose of Data Manager’s alerting facility is to alert you to storage-related events that occur within your environment. After you have defined the events or conditions for which you want to be alerted, you can let Data Manager monitor your storage automatically.

SNMPFor users planning to make use of Data Manager’s SNMP trap alert notification capabilities, an SNMP Management Information Base (SNMP MIB) is included in the server installation.


The SNMP MIB can be found in the file in the default Data Manager installation directory:

� For Windows: \Program Files\IBM\TPC\Data\snmp\tivoliSRM.mib� For UNIX or Linux: opt/IBM/TPC/Data/snmp/tivoliSRM.MIB

The MIB is provided for use by your SNMP management console software (for example, IBM Tivoli NetView® or Hewlett-Packard (HP) Openview). This MIB allows you to better view Data Manager-generated SNMP traps from within your management console software.

For sending SNMP traps, there must be an SNMP service installed and running on the Data Manager server. To check if there is an installed and running SNMP service, do these steps:

� For Windows:

a. Right-click My Computer.b. Click Manage.c. Click Services.

� For UNIX or Linux:

a. For information about whether SNMP is running and if so, on which port, check in /etc/services.

The default community name used by Data Manager to forward SNMP traps is public.

Integration with Tivoli Enterprise ConsoleTotalStorageProductivity Center for Data can use the Event Integration Facility (EIF) to send messages to the IBM Tivoli Enterprise Console (TEC), which allows TEC to consider TotalStorageProductivity Center for Data alerts in causal analysis for problems. TEC is added as a destination for alerts, in addition to the Simple Network Management Protocol (SNMP) Trap and the Windows Event Log. The event definitions are specified in the tivoliSRM.baroc file (provided by Data Manager), which is provided on the Data Manager installation CD. The tivoliSRM.baroc file must be loaded to the active rule base running on the TEC server. Based on the event definitions, the TEC administrator can write its own correlation and automation rules for events sent by Data Manager. You have to provide the TEC server name and the TEC port to start sending events to the TEC server.


Figure 1-6 Edit Alert Disposition window

Note: To configure event forwarding to TEC by e-mail or by SNMP Trap (used for sending events to Tivoli NetView and HP Openview), you need to configure Alert Disposition in the Data Manager GUI. See Figure 1-6 on page 26 for an example of the Alert Disposition window.


Integration with Tivoli Storage ManagerIntegration between TotalStorageProductivity Center for Data and IBM Tivoli Storage Manager produces two capabilities:

� The definition of a constraint violation is a means by which an administrator can enforce a request to have IBM Tivoli Storage Manager archive or back up the n largest violating files. Another type of constraint violation is to define acceptable and unacceptable uses of storage systems. For example, you can define a constraint to prohibit storing MP3 files on a file server. Productivity Center for Data currently reports on the n largest of the files that violate the constraint (where n is configured by the administrator).

� Even the regularly run file reports can be modified to allow administrators to archive or backup selected files directly as an outcome of the reports. These file reports can identify, for example, a filesystem’s largest files, orphaned files, and duplicate files. A storage administrator can use this feature to quickly free storage by archiving and deleting selected files.

These integration point variants can provide support for:

� IBM Tivoli Storage Manager archive with the option of deleting the file after a successful archive

� IBM Tivoli Storage Manager incremental and selective backups

The results of the IBM Tivoli Storage Manager backup-archive commands are viewable through the graphical user interface (GUI). In the case of constraints configured to archive-backup violating files, the results are included in the agent scan job logs (scans are responsible for enforcing constraints). In the case of file report driven archive-backup operations, a new type of job (archive-backup job) is created. You can view the results of the backup operations in this case in the archive-backup job logs.

1.4.6 Tivoli Common agent Services Tivoli Common agent Services provides a way to deploy multiple agent code across multiple user machines or application servers throughout your enterprise. The deployed agent code collects data from and performs operations on managed resources on behalf of a management application.

The Tivoli Common agent Services provides an Agent Manager that provides authentication and authorization and maintains a registry of configuration information about the agents and resource managers in your environment. The Resource Manager is a part of the Tivoli Common agent Services and is the server component of products that manage subagents deployed on the Common agent.


The Tivoli Common agent Services also provides Common agents to act as a container to host product subagents and common services. The Common agent provides remote deployment capability, shared machine resources, secure connectivity, and a single-entry point on the client computers on which the agents reside.

Figure 1-7 shows all of these components and how they interact.

Figure 1-7 Common agent Services infrastructure

In Figure 1-7, you can see a simplified diagram showing the two most important services that the Agent Manager provides. You can see that the Agent Manager is the central element in the Common agent Infrastructure.

Also shown are the ports that are used for these services. You can obtain a more detailed list of all of the ports and their relationships in the IBM TotalStorage Productivity Center for Data Installation and Configuration Guide, GC32-1774.

IBMCDB

ResourceManager

Data Agent Fabric Agent

Common Agent

Holds the registration of all agents and resource managers

DeviceServer

DataServer

ResourceManager

Registration Service

Recovery Services

Agent Manager

Application Server

Ports:9511 - registration9512 - authentication9513 - updates

Ports:80 - recovery 9513 - alternate for recovery


1.4.7 Role-based administrationThis section describes the role-based administration that you must consider when installing Data Manager.

TotalStorage Productivity Center and its Data Manager component support mainly two types of users, the operator and the administrator users. The type of user determines how each type uses Data Manager.

You implement the types of users by introducing a mapping between the roles within TotalStorage Productivity Center and the groups, which are in place at the operating system level of your TotalStorage Productivity Center server:

� Operator users: These users view the data collected by Data Manager. They can create, generate, and save reports.

� Data Manager administrators: These users can:

– Create, modify, and schedule pings, probes, and scans

– Create, generate, and save reports

– Perform administrative tasks and customize the Data Manager environment

– Create groups, profiles, quotas, and constraints

– Set alerts

1.5 Supported levels for Version 3 Release 3For a list of the supported systems, platforms, and other related operating system information, use the following links to ensure that you have the latest information:

� TotalStorage Productivity Center Version 3 Release 3 Supported Product List - IBM Storage:

http://www-01.ibm.com/support/docview.wss?rs=1103&uid=ssg1S1003286

� TotalStorage Productivity Center Version 3 Release 3 Platform Support - Agents, GUI, and Server:





Generic SMI-S array reporting and SNIA CTP certification This feature enables Data Manager to discover, monitor, enforce policies, alert upon, and report upon any disk array subsystems whose providers are Conformance Testing Program (CTP)-certified by Storage Networking Industry Association (SNIA) for Storage Management Initiative Specification (SMI-S) V1.0.2 and SMI-S 1.1.

Data Manager supports basic reports for any vendor’s disk subsystem that has been SNIA CTP-certified.

Support for disk array subsystems includes reports that show information gathered only through SMI-S, including subsystem manufacturer, model, LUNs, storage pools, disk drives (for providers that support the disk drive subprofile), and HBA Port worldwide name (WWN) to LUN assignments (for providers that support the LUN masking and mapping subprofile).

Prerequisite software to be installed in advanceThe following software is required before installing TPC V3.3.2:

� DB2 Version 8.2 with Fix Pack 14 and above or DB2 Version 9.1 with Fix Pack 4 and above.

� Agent Manager Version 1.3.2

With this release, Agent Manager is optional. If you decide at a later date to install the Agent Manager, you can do so. After you install the Agent Manager, you must register the Device server and Data server with the Agent Manager before installing the Data agents and Fabric agents, but we would recommend installing Agent Manager first before installing TPC.

Tivoli Common agent Services Tivoli Common agent Services supported levels are:

� The database for the Agent Manager supports only DB2 UDB.

� Only Agent Manager Version 1.3.2 is supported. If you upgrade from Version 1.2.x, it is mandatory that you upgrade to Version 1.3.2, because the embedded WebSphere shipped with Agent Manager Version 1.2 is no longer supported.

WebSphere Application Server TotalStorageProductivity Center now supports IBM WebSphere Application Server Embedded Express V6.0.2. which gets installed along with Agent Manager.


1.6 System Storage Productivity Center (SSPC) The IBM System Storage Productivity Center (SSPC) is an integrated offering that provides a consolidated focal point for managing IBM storage products as well as managing mixed-vendor storage environments. SSPC provides enhancements to daily storage administration by making available a broader set of configuration functions.

SSPC provides the GUI and utilities to configure these devices and enhancements to provide a broader set of management functions.

The SSPC combines the power of a customized IBM System x server with preinstalled storage software that represents a significant point of centralized management. SSPC enhances several rudimentary device utilities for easier, more intuitive, context based administration and on the whole lowers resource impacts. Key benefits include:

� Storage topology viewer for a “big picture” perspective

� Asset and capacity reporting aimed at improved capacity utilization

� Reduces storage complexity and improves interoperability

� Automatic device discovery

Supported devices:

� IBM System Storage DS8000 series

� IBM System Storage DS3000, DS4000, and DS5000 series

� IBM System Storage SAN Volume Controller

� IBM System Storage TS3310 and TS3500 Tape Libraries


Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data

Before deploying TotalStorage Productivity Center for Data, you need to analyze your environment to ensure that the system requirements have been met.

In this chapter, we provide information about TotalStorage Productivity Center for Data system requirements and prerequisites.

2


2.1 Installation prerequisites

This section lists the minimum prerequisites. In our ITSO residency, we installed all TotalStorage Productivity Center components on a single computer.

2.1.1 HardwareFor Windows and Linux on Intel®, IBM System x server, or other Intel technology-compatible platforms, the hardware requirements are:

� Server:

– Intel: Dual processor 3.2 GHz or faster processors.

– 4 GB of RAM.

– Network connectivity is required. Multiple NIC cards are not supported on the IBM TotalStorage Productivity Center server. If you do have multiple NIC cards, you must make sure that the first NIC card in the list is the one that all the agents can communicate with.

� Agent:

– Pentium® 400 MHz processor or higher.

– 256 MB of RAM.

For AIX on IBM System i® and IBM System p servers:

� Server:

– System p: Dual p5.

– 4 GB of RAM.

– Network connectivity is required. Multiple NIC cards are not supported on the IBM TotalStorage Productivity Center server. If you do have multiple NIC cards, you must make sure that the first NIC card in the list is the one that all the agents can communicate with.

� Agent:

– 400 MHz processor or higher.

– 256 MB of RAM.


2.1.2 Disk spaceThe Windows requirements are:

� Server:

– 4 GB of available disk space for the code and up to approximately 80 GB of hard disk space for databases

– 500 MB in the Windows temporary directory

� Data or Fabric Agent

100 MB of hard disk space for each agent. For a remotely installed Data agent, the temporary space required is 250 MB.

The UNIX or Linux requirements are:

� Server:

– 80 GB of hard disk space

– 500 MB in /tmp and 2 GB in /opt

� Agent

100 MB of hard disk space

Linux on IBM System z® requirements:

� Data or Fabric Agent

100 MB of hard disk space for each agent. For a remotely installed Data agent, the temporary space required is 250 MB.

Note: To determine the installed memory and processor type on a specific Windows machine, display system properties in the GUI by right-clicking My Computer and selecting Properties.

Use the uname -ar command to determine machine information about a specific AIX machine.

Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 35

2.2 Software prerequisites

Table 2-1 shows the platforms that are supported by TotalStorage Productivity Center server and agent components. We have included information for all of the TotalStorage Productivity components for completeness and for your future planning considerations.

Table 2-1 Platform support for Data server, Device server, Agents, GUI, and Agent Manager

Platforms Data server, Device server, database schema, and command-line interface (CLI)

Data agent and Fabric agent

GUI Agent Manager V1.3.2

IBM AIX 5L V5.1(32-bit)

No Yes with AIX 5100-05 maintenance level

No No


No Yes in 32-bit compatibility mode with AIX 5100-05 maintenance level

No No

IBM AIX 5L(32-bit)


No No

IBM AIX 5L(64-bit)


No No



No No



No No


Yes with AIX 5300-01 maintenance level and APAR IY70336

Yes with AIX 5300-01 maintenance level and APAR IY70336

Yes Yes



Yes in 32-bit compatibility mode with AIX 5300-01 maintenance level and APAR IY70336

Yes in 32-bit compatibility mode with AIX 5300-01 maintenance level and APAR IY70336

Yes Yes in 32-bit compatibility mode

IBM AIX V6.1(32-bit)

Yes Yes Yes Yes

IBM AIX V6.1(64-bit)

Yes in 32-bit compatibility mode

Yes in 32-bit compatibility mode

Yes Yes in 32-bit compatibility mode

Solaris 8 No Yes No No

Solaris 9 No Yes No No

Solaris 10 No Yes (agent must run in global zone; non-global or local zone is not supported.)

No No

HP-UX 11 and 11i No Data agent, Fabric agent on HP-UX 11i

No No

HP-UX 11 and 11i.2 No Yes No No

Windows 2000 Advanced Server

No Yes Yes No

Windows 2000 Datacenter

No Yes Yes No

Windows Server® 2003 Standard Edition

Yes Yes Yes Yes

Windows Server 2003 Enterprise Edition

Yes Yes Yes Yes

Red Hat Enterprise Linux AS Version 3.0 on System x

Yes Yes Yes Yes





Red Hat Enterprise Linux AS Version 3.0 on System p on POWER5™

No Data agent No No

Red Hat Enterprise Linux AS Version 3.0 on System i on POWER® 5

No Data agent No No

Red Hat Enterprise Linux AS Version 4.0 on System x

Yes Yes Yes Yes

United Linux 1.0 on System x

No Data agent No Yes

United Linux 1.0 on System z


SUSE LINUX Enterprise Server 8, System p on POWER, 4, and System x


SUSE LINUX Enterprise Server 9, System x, System p on POWER 5, System i on POWER 5, and System z

No Data agent runs on all series; Fabric agent runs on System x only.

No Yes

Supported Guest O.S. on VMware ESX Environment






2.2.1 Novell NetWare considerationsTo use Data Manager with NetWare servers, you must install the agent on a Windows computer where the Novell NetWare client is located. Data Manager performs discovery and scans from these Windows computers by using NetWare calls. When the agent is installed on a Windows computer, the agent first determines whether a NetWare client is installed. If a NetWare client is installed, the following steps occur:

1. The agent performs an initial probe and requests a list of the Novell Directory Services (NDS) trees from the NetWare client (the NDS trees that are accessible to that agent).

Because a NetWare client is installed, you do not need special NetWare permissions to generate a list of your NDS trees. However, Data Manager requires permissions to the NDS trees when performing discovery and scan jobs of those trees.

2. The agent reports the list of NDS trees to the server.

Before you run a discovery or scan job, you must configure login IDs and passwords for the NDS trees by selecting Administrative Services → Configuration → NetWare Tree Logins.

2.2.2 NAS environment considerationsThis section contains the requirements for installing and running Data Manager within an NAS environment.

Agent requirementsWhen installing Data Manager in an NAS environment, you must install the agent on a machine that has access to the NAS filers within your environment that you want to monitor:

� Windows

The agent that is logging in to and scanning the NAS filer is not required to be in the same domain as the user or the NAS filer. If you install the agent on a another domain from the NAS filer, the agent scans the NAS filer if the domain of the agent computer is a “trusted domain” by the domain of the NAS filer.

� UNIX and Linux

The agent computer must import the NAS filer’s exports as NFS mounts (or automounts on Solaris).


NAS The NAS filers within your environment must be visible to the machines where you install the agent or agents. If you want to monitor NAS filers from Windows, you must configure those NAS filers to be members of a Windows domain.

2.2.3 VMware environment considerationsIBM TotalStorage Productivity Center supports the VMware Virtual Infrastructure, which consists of the ESX Server and VMware VirtualCenter.

The ESX Server is a true hypervisor product that can host multiple virtual machines that run independently of each other while sharing hardware resources.

The VirtualCenter is the management application that centralizes the management and monitoring of multiple ESX Servers in a data center.

Planning for VMware Environment� IBM TotalStorage Productivity Center supports the following:

– ESX Server V3.0.1 or later (LUN correlation is not supported.)

– VMware VirtualCenter V2.0.1 or later (LUN correlation is not supported).

– ESX Server V3.5 or later (LUN correlation is supported.)

– ESX Server V3.5 3i or later (LUN correlation is supported.)

– VMware VirtualCenter V2.5 or later (LUN correlation is supported.)

Note: You do not install agents to the NAS filers themselves. For IBM 5196 TotalStorage Network Attached Storage 300 G machines only, we recommend that you install the agent directly on those machines. If the 300 G is clustered, you need to install an agent on each local node.


� The supported guest operating systems that can be run on a virtual machine are those that are supported both by the Data agent and the ESX Server. The supported products and versions are:

– Windows Server 2003 Standard and Enterprise Editions withService Pack 1

– Windows 2000 Advanced Server

– Red Hat Enterprise Linux Advanced Server 3.0 and 4.0 with the following updates:

• Updates 4, 5, 6, and 7 for 32-bit machines

• Updates 4, 5, 6, and 7 for 64-bit machines

– SUSE Linux Enterprise Server 8 and 9 with the following service packs:

• Service packs 1, 2, and 3 for 32-bit machines

• Service packs 1, 2, and 3 for 64-bit machines

– SUSE Linux Enterprise Server 8 with service packs 1, 2, 3, and 4

� To utilize the improved VMware support, two data sources are required. VMware Virtual Infrastructure data source is needed for the ESX Server and a TPC Data agent is required on each virtual machine you plan to monitor. For full functionality, both the Data agent and Virtual Infrastructure must be up and running. If one of the items is not present in a specific environment, only a limited picture is presented and certain virtual machines might not be recognized.

What is VMware LUN Correlation? VMware LUN Correlation allows you to:

� Visualize end-to-end mapping of storage from subsystem to volumes assigned to VMware guest operating systems.

� View storage utilization and perform impact analysis at the virtual server level.

� Enables faster time to resolution for problems associated with storage volumes on VMware guests.

� Quickly determine status for all components associated with a storage volume.

For additional information about LUN Correlation, refer to 5.8, “VMware ESX Server support” on page 529.


� No IBM TotalStorage Productivity Center component can be installed directly on the ESX Server (Service Console).

� No HBA virtualization is available for the VMware virtual machines. Therefore, if you install a Fabric agent on a VMware virtual machine, the Fabric agent will not be useful.

� No events directly generated by the Virtual Infrastructure will be supported.

� No VMware clusters will be supported.

� The storage subsystems supported through VMware are:

– IBM System Storage DS4000



– SAN Volume Controller

– Enterprise Storage Server (ESS)

– Hewlett Packard Enterprise Virtual Arrays (EVA)

– Hitachi Data Systems 9xxxx

– EMC Symmetrix

– EMC CLARiiON

– 3PAR

� Data path explorer is not supported for VMware ESX Server and virtual machines.

� Before you can display reports or see the topology for VMware Virtual Infrastructure, you must configure TPC for VMware environment. To configure TPC for VMware Environment, refer to “Configuring TPC communication to VMware” on page 347.

2.2.4 IPv6 considerationsTotalStorage Productivity Center supports Internet Protocol Version 6 (IPv6) for communication between its components. You can install and run IBM TotalStorage Productivity Center on computers that are enabled for IPv4, IPv6, or dual stack.

Attention: There is no need to install a Data agent on the VMware ESX server itself. This feature is not supported.


Installation scenarios for TotalStorage Productivity CenterWe illustrate the scenarios and the general steps when installing the product.

IPv6-only installation scenarioIn this scenario, install IBM TotalStorage Productivity Center on a computer configured for IPv6-only. Agent Manager, Data agents, and Fabric agents are disabled because they do not communicate over IPv6. Do these steps:

1. Use either of the following methods when installing IBM TotalStorage Productivity Center components:

a. Method 1: Install the GUI, CLI, Data server, Device server, and database repository components on a local, IPv6-only configured computer.

b. Method 2: Install the database repository on a remote IPv6-only computer, and the GUI, CLI, Data server, and Device server on a local, IPv6-only computer.

If you want to connect to a remote database repository using the IPv6 protocol, you must use DB2 Database V9.1 Fix Pack 2 or later for the database repository.

2. Run the user interface from an IPv6-only or dual stack configured computer. You cannot run the user interface from a computer configured for IPv4-only.

3. Configure communication to other IBM TotalStorage Productivity Center servers (for rollup probes and reporting), SMI-S CIM agents, out-of-band Fabric agents, and storage devices operating in IPv6 or dual stack mode. You cannot configure communication from TotalStorage Productivity Center that is installed on an IPv6-only system to storage entities on IPv4-only systems.

4. Launch element managers on IPv6-only computers from the Topology Viewer, Element Management perspective, Disk Manager, or external tools command.

Note: Not all the functions are available in an IPv6-only environment. For more information about what functions are not available, refer to “General Planning” in the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.


IPv6 and IPv4 (dual stack) installation scenarioDual stack indicates that a machine has both the IPv4 and IPv6 stacks enabled and both addresses configured. In this scenario, install IBM TotalStorage Productivity Center on a computer where both IPv4 and IPv6 are configured:

1. Use any of the following methods when installing TotalStorage Productivity Center components:

a. Method 1: Install the GUI, CLI, Data server, Device server, and database repository components on a local, dual stack computer.

b. Method 2: Install the database repository on a remote IPv4-only computer, and the GUI, CLI, Data server, and Device server on a local, dual stack computer.

c. Method 3: Install the database repository on a remote IPv6-only computer, and the GUI, CLI, Data server, and Device server on a local, dual stack computer. You must use the DB2 Database V9.1 Fix Pack 2 or later for the Linux or UNIX for the database repository. This database is IPv6 enabled and is used for the database repository.

2. Register with the Agent Manager running on a computer in IPv4 or dual stack mode.

3. Install Data and Fabric agents remotely on computers that are running IPv4 or dual stack mode.

4. Run the user interface from an IPv4-only, IPv6-only, or dual stack computer.

5. Configure communication to other IBM TotalStorage Productivity Center servers (for rollup probes and reporting), SMI-S CIM agents, out-of-band Fabric agents, and storage devices operating in IPv4, IPv6, or dual stack modes.

6. Launch element managers on IPv6-only, IPv4-only, and dual stack computers from the Topology viewer, Element Management perspective, Disk Manager, or external tools command.

2.3 Databases supported

At the time of writing this book, we used the information at the following Web site as a reference:

http://www-01.ibm.com/support/docview.wss?uid=ssg1S1003285



2.3.1 Data Manager database repositoryData Manager stores information about storage assets in the centralized repository. The repository is organized into a series of relational database tables and is accessed by Data Manager using Java Database Connectivity (JDBC). The Data Manager repository is supported on DB2 Enterprise Server Edition Version 8.1 with Fix Pack 14 or higher or DB2 Enterprise Edition Version 9.1 with Fix Pack 2 or higher are supported for local and remote installation.

When you install IBM TotalStorage Productivity Center, a single, shared database instance is created on DB2 for the Data server and the Device server. The default database name is TPCDB.

2.3.2 Agent Manager database repositoryThe Agent Manager database repository is supported only on the following database; DB2 Enterprise Server Edition Version 8.1 with Fix Pack 14 or higher is supported for local and remote installation or DB2 Enterprise Edition Version 9.1 with Fix Pack 2 or higher.

There is only one database instance that is created for IBM TotalStorage Productivity Center on DB2. The Agent Manager repository uses its own database. The default name of this database is IBMCDB.

It is possible to use only one database, IBMCDB, for both repositories, but we do not recommend this configuration.

2.3.3 SMS or DMS tablespace typeAt installation time, you can specify whether the DB2 database is system-managed space (SMS) or database-managed space (DMS).

In SMS, the filesystem manager for the operating system allocates and manages the space where the table is stored. Several of the advantages of an SMS tablespace are:

� Space is not allocated by the system until it is required.

� Creating a database requires less initial work, because you do not have to predefine containers. A container is a physical storage device and is assigned

Note: We recommend that you install a single instance of IBM DB2 UDB Enterprise Server Edition Version 8.1 with Fix Pack 14 or higher as your repository for both the Agent Manager and IBM TotalStorage Productivity Center.


to a tablespace. A single tablespace can span many containers, but each container can belong to only one tablespace.

In DMS, the database manager controls the storage space. The administrator decides which devices to use, and DB2 manages the space on those devices. However, we recommend that you select SMS.

Several of the advantages of a DMS tablespace are:

� The size of a tablespace can be increased by adding containers. Existing data is automatically rebalanced across the new set of containers to retain optimal I/O efficiency.

� A table can be split across multiple tablespaces, based on the type of data being stored (long field data, indexes, or regular table data).

� The location of the data on the disk can be controlled, if this function is allowed by the operating system.

� If all table data is in a single tablespace, a tablespace can be dropped and redefined with less impact than dropping and redefining a table.

� In general, a well-tuned set of DMS tablespaces outperforms SMS tablespaces.

We recommend that you select the SMS tablespace format.

2.3.4 Database Migration UtilityYou can upgrade previous releases of TotalStorage Productivity Center to Version 3.3. You cannot upgrade Fabric Manager V2.x, Disk Manager V2.x, or Performance Manager V2.x.

You can, however, migrate the DB2 data from the Fabric Manager, Disk Manager, and Performance Manager. You can upgrade the following IBM TotalStorage Productivity Center releases to IBM TotalStorage Productivity Center Version 3.3:

� IBM TotalStorage Productivity Center for Data Version 2.3 to 3.3

� IBM TotalStorage Productivity Center Version 3.1.1, 3.1.2, or 3.1.3 to 3.3

� IBM TotalStorage Productivity Center Version 3.2 or 3.2.1 to 3.3

Note: Do not forget that there is no direct migration path from Version 2.3 to 3.3. You must first migrate to Version 3.1.3/3.2.1, and then upgrade to 3.3.


If you have data that you want to migrate from IBM TotalStorage Productivity Center V2.x to V3.x, you can run the Data Migration Utility after you install TotalStorage Productivity Center. A new Migration Utility is available. When you migrate data to IBM TotalStorage Productivity Center Version 3.3, follow the instructions in Chapter 5 in the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.

For additional information about the Data Migration Utility, refer to the IBM TotalStorage Productivity Center Flash at this Web site:

http://www.ibm.com/servers/storage/support/software/tpc

2.3.5 Data agent-monitored databasesThe Data agent can monitor these Relational Database Management Systems (RDBMSs):

� DB2 V7.2

� DB2 V7.2 with Fix Pack 8

� DB2 v8.1 with Fix Pack 9

� DB2 V8.2 (the same as DB2 V8.1 with Fix Pack 7a)

� DB2 v8.2 with Fix Pack 11

� DB2 v9

� Microsoft SQL Server® 7.0

� Microsoft SQL Server 2000

� Oracle® 8i

� Oracle 9i

� Oracle 10g

� Sybase

2.4 Pre-installation steps for WindowsThe prerequisite components for IBM TotalStorage Productivity Center V3.3 are:

� IBM DB2 UDB Enterprise Server Edition V8.2 Fix Pack 14 or higher

� Agent Manager V1.3.2



2.4.1 Installable componentsAfter you install TotalStorage Productivity Center V3.3, you have the following installable components available:

� Database schema� Data server� Device server� Graphical User Interface (GUI)� Command Line Interface (CLI)� Data agent� Fabric agent

The CLI is considered optional. The Data agent and Fabric agents are likely be installed in multiple locations. The GUI is installed wherever you want to control TotalStorage Productivity Center.

2.4.2 Order of component installationInstall the components in the following order:

1. DB22. Agent Manager3. TotalStorage Productivity Center components

2.4.3 Server recommendationsThe IBM TotalStorage Productivity Center for Data server component acts as a traffic controller for directing information and handling requests from the agent and UI components that are installed within an environment. You need to install at least one server within your environment.

If you have 500 or more agents in your environment, follow these steps:

1. Probe the machines at least one time a day (or more depending on when you want to test for alert conditions (other than directory alerts, quotas, or constraints).

Tip: We recommend that you install the database schema first, then install the Data server and Device server in a separate step.

If you install all of the components in one step and if any part of the installation fails for any reason (for example, insufficient space or incorrect passwords), the installation suspends and rolls back, uninstalling all of the previously installed components.


2. If you use anything other than __ALL__ groups (ALL filesystems, ALL computers), you must manually populate the groups.

3. Always run a probe before a scan. Set the following parameters in the server.config file:

MaxConnections=1200: The default is 500. Agents can have multiple connections to the server.

routerThreads=3 (max): Incoming connections need to be routed to the correct Data Manager service queue and can stack up behind this thread. You can watch this happen by watching the connections in the server service and the agent service in the GUI. The server service runs the router, and the agent service is where the connections will queue up when routed to be saved by any of three threads to the repository.

4. Set the following parameter in the Scheduler.config file:

MaxSubmitthreads=8: This parameter tells how many threads are used to tell the agents to start a job. Agent connections can queue up the scheduler service. After a job is run, the agent makes a connection to communicate with this thread to give it the job status.

2.4.4 Installation port requirementsIBM TotalStorage Productivity Center uses TCP/IP ports for communication, as shown in Table 2-2. These ports must be opened and available for use.

If there is a firewall between the Agent Manager, the agents, and the resource managers in your deployment, you must open the ports for TCP traffic as indicated in the table.

Table 2-2 Port requirements

Note: We recommend that you do not manage more than 1000 agents with a single server. If you need to install more than 1000 agents, install an additional server for those agents to maintain optimal performance. If you have a TotalStorage Productivity Center Standard Edition V3.3 license, implement the Rollup Report feature to gather reports from the subordinate TPC servers to the master TPC server.

Component Server perspective Firewall port Agent perspective

Data server Inbound/Outbound 9549 N/A

Device server Inbound/Outbound 9550 N/A

Common agent Session Initiator=YesOutbound

9510 Session Initiator=NoInbound


Agent Manager - secure SSLRegistering agentsRegistering resource manager

Session Initiator=NoInbound

9511 Session Initiator=YesOutbound

Agent Manager - secure SSL with client authenticationProviding configuration updatesRenewing and revoking certificatesQuerying the registry for agent informationRequesting ID resets

Session Initiator=YesInbound and Outbound

9512 Session Initiator=NoInbound and Outbound

Agent ManagerRequesting updates to the certificate revocation listRequesting Agent Manager informationDownloading the truststore fileAlternate port for the Agent Recovery Service

Session Initiator=NoInbound

9513 Session Initiator=YesOutbound

Common agent (No access needed)

N/A 9514 Local to Server

Common agent (No access needed)

N/A 9515 Local to Server

Common Information Model Object Manager (CIMOM) HTTP

N/A 5988 N/A

CIMOM HTTPS N/A 5989 N/A

Agent Recovery Service Session Initiator=NoInbound

80 Unsecured connection for Agent Recovery Service action

Push UNIX Session Initiator=YesOutbound

SSH(22) Session Initiator=NoInbound and Outbound

Push Windows Session Initiator=YesOutbound

NetBIOSsessions service (139)

Session Initiator=NoInbound and Outbound


RSH (514) Session Initiator=NoInbound and Outbound



For the Dater server, you need to reserve two ports, one for the Data server inbound server port plus another port that is 10 greater than the Data server port (9549). For example, if the Data server port is 9549, then another port would be 9549+10 or 9559.

If you want to choose a port other than the default 9510 for Common agent communication, make sure that the port you choose, and the ports higher than it, are available for use. For example, if N represents the open port that you want to use, ensure that ports N+4 and N+5 are open as well.


REXEC (512) Session Initiator=NoInbound and Outbound

Push UNIX Session Initiator=YesInbound

601 N/A

Push All Session Initiator=YesInbound

High ports 3000+

Session Initiator=NoInbound and Outbound

Push All Session Initiator=YesInbound

TPC for Data server 2078

N/A

Simple Network Management Protocol (SNMP) Listener Port

N/A 162 N/A

Service Location Protocol (SLP) N/A 427 N/A


Note: To list the ports in use, run the following commands:

� For Windows:

netstat -an

� For UNIX and Linux:

netstat -an | grep LISTEN


You can find the port numbers used on your system by running the command netstat -a or netstat -ano (to see the PID using that port, too), as shown in Figure 2-1 and Figure 2-2 on page 53.

Figure 2-1 netstat -a sample


Figure 2-2 netstat -ano sample


2.4.5 Supported filesystemsTotalStorage Productivity Center for Data supports monitoring and reporting of the following filesystems:

� Journaled filesystem (JFS), JFS2.

� EXT2.

� EXT3.

� File allocation table (FAT).

� FAT32.

� HP-UX HFS filesystem.

� Network Filesystem.

� NTFS4.

� NTFS5.

� NetWare_FAT.

� NetWare_NSS.

� REISERFS.

� IBM TotalStorage SAN Filesystem.

� Network Appliance Data ONTAP® V7, including flexible volumes (FlexVol®). FlexVol enables you to create multiple flexible volumes on a large pool of disks.

� TMPFS.

� UNIX filesystem (UFS).

� VXFS.

� WAFL®.

2.4.6 Supported network filesystemsData Manager currently supports the monitoring and reporting of the following networked filesystems:

� IBM TotalStorage SAN Filesystem V1.0 (Version 1 Release 1), from AIX 5L V5.1 (32-bit) and Windows 2000 Server and Windows 2000 Advanced Server clients

Note: Filesystem extension is supported for JFS filesystems running on AIX 5L V5.1 and VxFS filesystems running on Sun Solaris 2.8.


� IBM TotalStorage SAN Filesystem V2.1 and V2.2 from AIX 5L V5.1 (32-bit), Windows 2000 Server and Windows 2000 Advanced Server, Red Hat Enterprise Linux 3.0 Advanced Server, and SUN Solaris 9 clients

� General Parallel Filesystem (GPFS™) V2.1 and V2.2

2.4.7 Support for NAS/NetWare Data Manager currently supports the monitoring of the following NAS/NetWare devices:

� Novell NetWare 5.1 or higher� NetApp® Data ONTAP

NAS devices other than Network Appliance Filers must meet the following criteria to be supported by this product:

� If scanned from a UNIX agent, an NAS device must support NFS queries.

� If scanned from a Windows agent, an NAS device must support Common Internet Filesystem (CIFS) queries.

� A NAS device must support SNMP queries (such as sysName and sysOID).

� A NAS device must supply a unique sysName.

2.4.8 Disk and volume group support Data Manager supports the monitoring of the following volume managers:

� Veritas Volume Manager on Sun Solaris� Veritas Volume Manager on HP-UX� AIX Logical Volume Manager (LVM)� HP-UX Logical Volume Manager

These volume managers enable you to create groups of logical volumes and disks. You can generate a variety of reports for these disk and volume groups.

Note: Disk and volume group information appears in Data Manager → Reporting → Asset → By Computer and Asset → System-wide reports.


2.4.9 Storage subsystem supportTotalStorage Productivity Center V3.3 supports IBM and third-party disk systems that are Storage Management Interface Specification (SMI-S) V1.0.2, SMI-S 1.0.3, or SMI-S 1.1 compatible. This support includes storage provisioning, as well as asset and capacity reporting. TotalStorage Productivity Center V3.3 implements many of its disk, tape, and fabric management functions through exploitation of the SMI-S 1.0.2, SMI-S 1.0.3, and SMI-S 1.1 levels of the standard. SMI-S 1.1 supports all of the functions of SMI-S 1.0.2 plus additional functionality (for example, performance management). These systems include, but are not limited to:

� IBM TotalStorage SAN Volume Controller (SVC)

� IBM TotalStorage Enterprise Storage Server (ESS)

� IBM TotalStorage Disk Subsystems (DS3400, DS4000, DS6000, and DS8000 series)

� FAStT

� Disk array subsystems whose providers are Conformance Testing Program (CTP)-certified by Storage Networking Industry Association (SNIA) for SMI-S 1.0.2

For the latest and most complete storage subsystem support information, go to to the following Web site and follow the appropriate links:

http://www-1.ibm.com/servers/storage/support/software/tpc/

For a complete list of SMI-S conforming provider companies, go to the following Web site:

http://www.snia.org/forums/smi/tech_programs/ctp/conformingproviders/

At the time of writing this book, the supported product list for TPC V3.3.2 could be found at the following address:


2.4.10 Tape library supportIBM TotalStorage Productivity Center V3.3 supports the following tape libraries:

� IBM TotalStorage 3494 Tape Library: The 3494 Tape Library can be used for data consolidation to help achieve higher performance and reduced requirements for tape drives and cartridges, environmental controls, and personnel. The 3494 Tape Library supports Write Once Read Many (WORM) and standard rewritable media, providing further opportunity for consolidation.


http://www-1.ibm.com/servers/storage/support/software/tpc/

http://www.snia.org/forums/smi/tech_programs/ctp/conformingproviders/


� IBM System Storage TS3500 Tape Library (formerly IBM TotalStorage 3584 Tape Library): The TS3500 Tape Library is designed to provide a highly scalable, automated tape library for mainframe and open systems backup and archive functions in midrange to enterprise environments.

� IBM System Storage TS3310 Tape Library: The TS3310 Tape Library is a modular, scalable tape library that is designed to grow as your needs grow. IBM TotalStorage Productivity Center supports IBM and non-IBM tape libraries through the SMI-S (CIM) agent, which assumes that the tape library supports the SMI-S 1.1 profile for tape libraries.

2.5 User IDs and securityThis section discusses the user IDs that are used during the installation and those user IDs that are used to manage and work with TotalStorage Productivity Center. It also explains how you can increase the basic security of various components.

2.5.1 User IDsThis section lists and explains the user IDs that are used in a TotalStorage Productivity Center environment.

Granting privileges Grant privileges to the user ID that is used to install the TotalStorage Productivity Center components.

These user rights are governed by the local security policy and are not initially set as the defaults for administrators. They might not be in effect when you log on as the local administrator. If the TotalStorage Productivity Center installation program does not detect the required user rights for the logged on user name, the program can optionally set them. The program can set the local security policy settings to assign these user rights. Alternatively, you can manually set them prior to performing the installation.

To manually set these privileges, follow these steps:

1. Select Start → Settings → Control Panel.

2. Double-click Administrative Tools.

3. Double-click Local Security Policy.


4. The Local Security Settings window opens. Expand Local Policies. Then, double-click User Rights Assignments to see the policies in effect on your system. For each policy added to the user, perform the following steps:

a. Highlight the policy to be selected.

b. Double-click the policy and look for the user’s name in the Assigned To column of the Local Security Policy Setting window to verify the policy setting. Ensure that the Local Policy Setting and the Effective Policy Setting options are selected.

c. If the user name does not appear in the list for the policy, you must add the policy to the user. Perform the following steps to add the user to the list:

i. In the Local Security Policy Setting window, click Add.

ii. In the Select Users or Groups window, under the Name column, highlight the user of group.

iii. Click Add to place the name in the lower window.

iv. Click OK to add the policy to the user or group.

5. After you set these user rights, either by using the installation program or manually, log off the system and then log on again for the user rights to take effect.

6. Restart the installation program to continue with the TotalStorage Productivity Center installation.

2.5.2 Increasing user securityThe goal of increasing security is to have multiple roles available for the various tasks that can be performed. Each role is associated with a certain group. The users are only added to those groups of which they need to be part in order to fulfill their work.

Role-based levels of usersThere are mainly two levels of users within TotalStorage Productivity Center: They are an Operator user and an Administrator for each of the specific work areas in IBM TotalStorage Productivity Center (Data, Fabric, Disk, and Tape).

In addition to these levels, there is a general TotalStorage Productivity Center administrator, who can work in all four areas as an administrator and, on top of that, is a so-called Superuser. This is the standard user with which you are working immediately after installing the product.


The level of these users determines how they can use IBM TotalStorage Productivity Center:

� Operator-type users:

– View the data collected by TotalStorage Productivity Center.

– Create, generate, and save reports.

� Administrator-type users:

– Create, modify, and schedule pings, probes, and scans.

– Create, generate, and save reports.

– Perform administrative tasks and customize the TotalStorage Productivity Center environment.

– Create groups, profiles, quotas, and constraints.

– Set alerts.

Microsoft Windows domain The Microsoft Windows domain and Active Directory® features are supported only on Windows 2000 Server and Windows Server 2003 with Windows domain or Active Directory configurations.

When you install the IBM TotalStorage Productivity Center agent, you can specify a domain name, which validates the account and password. If an account or group exists locally on the server, as well as in the domain directory, you must explicitly enter the domain name when you log in to the IBM TotalStorage Productivity Center GUI.

IBM TotalStorage Productivity Center requires that the accounts under which its services run have local Administrative rights.

By default, the IBM TotalStorage Productivity Center installation program grants the necessary rights to these accounts. However, if you are enforcing Group Policy in your Windows domain that might override this membership, be sure to make the necessary changes to your Group Policy to grant these accounts Administrative rights.

In order to login to the IBM TotalStorage Productivity Center GUI using the Windows Domain format you should specify <domain_name>\<domain_username>.


2.5.3 Certificates and key filesA TotalStorage Productivity Center environment uses certificates to ensure a high level of security. The security certificates can be generated during the installation of the Agent Manager component. During the installation, key files can be generated as self-signed certificates, but you must enter a password for each file to lock it, the certificate authority password. Although you can leave the password for the Certificate Authority file blank, we do not recommend it. If you leave this password blank, a random password is generated for you during the installation process and you are then unable to unlock the Certificate Authority file. We therefore recommend that you enter a password for this file, which allows you to unlock the Certificate Authority file later, if needed. The following certificate authority files in the directory are locked with the certificate authority password:

� CARootKeyRing.jks (private key ring of the certificate authority in the Agent Manager)

� agentManagerKeys.jks (contains the password to decrypt the private key ring file)

� CARootKey.pwd (contains the password to decrypt the private key ring file)

The \certs directory also contains the certificate authority truststore file (agentTrust.jks), which contains the signer certificate for the certificate authority. This file is locked with the agent registration password.

The default directory for the key file on the Agent Manager in a Windows environment is C:\Program Files\IBM\AgentManager\certs. In a UNIX or Linux environment, the default directory is /opt/IBM/AgentManager/certs.

Agent Manager certificatesThe Agent Manager comes with demonstration certificates that you can use. However, you can also create new certificates during the installation of Agent Manager (see Figure 3-35 on page 116).

If you choose to create new files, the password that you enter on the window, as shown in Figure 3-36 on page 117, as the Agent registration password is used to lock the agentTrust.jks key file. The default directory for that key file on the Agent Manager is <Agent_Manager_install_dir>\certs.

Note: Our recommendation is to use the demonstration certificate only in terms of a proof of concept installation. Always create a new certificate for your actual production environment.


There are more key files in that directory, but during the installation and first steps, the agentTrust.jks file is the most important one. This file is only important if you allow the installer to create your keys, which we recommend.

2.6 Services and service accounts

The managers and components that belong to the TotalStorage Productivity Center are started as Windows Services. Table 2-3 provides an overview of the most important services. To keep it simple, we did not include all of the DB2 services in the table. To start, stop, or restart one of the managers or components, you use the Services window under Control Panel → Administrative Tools. Table 2-3 shows a list of the services.

Table 2-3 Services and service accounts

Element Service name Service account

Comment

DB2 N/A db2admin The account needs to be part of the Administrators and DB2ADMNS groups.

Agent Manager IBM WebSphere Application Server V5 - Tivoli Agent Manager

LocalSystem You need to set this service to start automatically, after the installation.

Common agent IBM Tivoli Common agent - C:\Program Files\IBM\TPC\ca

itcauser N/A.

Productivity Center for Data

IBM TotalStorage Productivity Center - Data server

TSRMsrv1 N/A.

Productivity Center for Fabric

IBM WebSphere Application Server V5 - Fabric Manager

LocalSystem N/A.


2.7 Analyzing and defining environment requirements

This section describes what you must know before installing IBM TotalStorage Productivity Center for Data. Before you start to install the product, gather the required information and check the prerequisites:

� Grant the following privileges to the Windows user account that will be used to install the TotalStorage Productivity Center:

– Act as part of the operating system.– Create a token object.– Adjust memory quotas for a process.– Replace a process-level token.– Log on as a service.

� Identify any firewalls and obtain the required authorization to pass network traffic through them.

� Obtain the static IP addresses to use for the TotalStorage Productivity Center servers.

� Are the operating systems on the servers and client at the correct level to deploy components of IBM TotalStorage Productivity Center for Data?

For example for AIX, use the command oslevel to get information about the version and maintenance level of the AIX operating system.

On AIX, use the following command to determine if a required fix is installed:

instfix -ik fix_number

� Do the servers and workstations meet the appropriate hardware requirements in order to install IBM TotalStorage Productivity Center for Data components on them?

� Verify the network connectivity. Use these commands:

For Windows, UNIX, and Linux:

– ipconfig– ping

� Is there a correctly set up Domain Name System (DNS) service? In the Windows, UNIX, or Linux environment, you can use the command nslookup to verify TCP/IP name resolution. For an example of the output of this command in a Windows environment, see Figure 2-3 on page 63. You can enter host names to see if names are resolved properly.


Figure 2-3 Result of nslookup command

� Which ports are opened and ready for use? For example, in Windows, UNIX, or Linux environments, the command to check this item is netstat -an. For a sample result of this command, see Figure 2-2 on page 53.

� Agent Manager information is provided during the installation, including:

– Agent Manager name or IP address– Common agent password to register with Agent Manager– Resource Manager user ID and password to register with Agent Manager

� For the DB2 TotalStorage Productivity Center repository, you need the DBA user ID and password. Decide if you will use the defaults or provide unique user IDs and passwords based on system requirements.

� Are there storage subsystems that require that a vendor-specific Common Information Model Object Manager (CIMOM) be installed? For example, for a Hitachi Data system, check and install, if needed, the HiCommand application for a specific storage subsystem. You can check for required CIMOM vendor applications in the IBM TotalStorage Productivity Center Supported Products List found at:


2.8 Agent installation methodology

When you have finished gathering all of the required information about your environment and prepared a list of all required storage subsystems to be managed, consider the installation methods of your agents, which are required to manage your various storage subsystems. You must install a Data Agent on each machine containing storage that you want to monitor. The agent runs in the background and performs and interacts with monitoring jobs, such as pings, probes, and scans.



You can install the agent either locally or remotely.

2.8.1 Local installation of the agentThere are two methods to install an agent locally on a server that contains a storage subsystem.

Installation using GUITo locally install the agent, you must have a CD media containing the IBM TotalStorage Productivity Center for Data installation program (the installer program provides a Graphical User Interface (GUI) for installation purposes). To install the agent, you must have information about the:

� Data Manager server name and port (The default is 2078.)

� Agent Registration Password (The password that you specified when you were installing Agent Manager)

� Agent listening port (The default is 9510.)

Installation using the command lineThe local installation using the command line requires the same information as the local installation using GUI. To install an agent using the command line, you must run the installation program (setup.exe for Windows and setup.sh for UNIX and Linux) from the command line with all of the needed options specified. This method gives you the capability to install an agent on machines that do not have a configured display or do not already have the correct Java Runtime Environment (JRE™) environment variable set up, which might be needed to start the GUI. For further information, refer to IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.

2.8.2 Remote agent installationYou can remotely install agents to:

� Machines in the same domain or to machines in another domain.

� Windows, UNIX, and Linux machines.

� A target machine’s local drive. The local drive represents the administrative share, such as \\computer_name\c$. You cannot install the agent to a mapped drive, because the installation will fail and the installation program will report that there are no standard shares.


Before you remotely install an agent, gather the required information:

� The name and the port of Data Manager server.

� Agent Registration Password.

� The name and IP address of the machines on which you want to install the agent.

� When installing to a foreign domain, the domain from which you are installing has to trust the foreign domains, and your login must be an administrator on the local machine and a domain administrator on the foreign domain. Note that if you do not have administrator rights to the foreign domain, the installation will be able to find the other domains but might not be able to enumerate the computers for that domain.

� You must supply a user ID and password that have administrative privileges on the target machine.

Any remote installation process is always interactive, which means that it needs installation GUI access. For further information, refer to the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.

2.8.3 Virtual I/O Server agent installationYou can use TotalStorage Productivity Center agents to gather information about Virtual I/O Servers.

Planning for the Virtual I/O Server configurationThis topic provides information about planning for the Virtual I/O Server configuration. The Virtual I/O Server is part of the IBM System p Advanced Power Virtualization hardware feature and allows the sharing of physical resources between LPARs. A script enables you to silently install the Data and Fabric agents on a Virtual I/O Server. The script is run when you run the cfgsvc command. The script is located on the TotalStorage Productivity Center disk3 image for the agents. Consider the following to install the agent:

� TotalStorage Productivity Center supports Virtual I/O Server Version 1.5.2 or later.

� For POWER5 processor-based systems, a minimum of 512 MB of memory is required. For POWER6™ processor-based systems, a minimum of 768 MB of memory is required.

� The TotalStorage Productivity Center agent on Virtual I/O Server must have a minimum of 1 GB of memory.


� When installing the agents, ensure that there are no other operations running on the Virtual I/O Server. The machine that is running the TotalStorage Productivity Center agents require 100% of CPU time.

� You must be logged on with the padmin user ID to perform the installation of the agents, run commands to configure, and start and stop the agents.

� Once installed on a Virtual I/O Server, you cannot upgrade the Data and Fabric agents locally because of restrictions on the shell of the padmin user ID. However, you can upgrade them in the following ways:

– Upgrade Data agents by selecting Administrative Services → Configuration → Data Agent Upgrades in the TotalStorage Productivity Center user interface.

– Upgrade Fabric agents using remote fabric deployment in the TotalStorage Productivity Center installation program.

General procedure to install and configure agentsThe general steps to install and configure the agents on the Virtual I/O Server are:

1. Install TotalStorage Productivity Center or upgrade to V3.3.2.90 or later.

2. Install and configure the agents on the Virtual I/O Server by running the cfgsvc command.

3. When you install the agents, they are automatically started.

4. Run a discovery job for the agents on the Virtual I/O Server.

5. Collect information about a Virtual I/O Server by running probes, scans, and ping jobs.

6. View the storage information gathered by the monitoring jobs through the topology viewer and reports that you can generate through Fabric Manager and Data Manager.

2.9 Interoperability namespace summary table

The interoperability namespace for a CIMOM is discoverable through Service Location Protocol (SLP) and is automatically populated in the TotalStorage Productivity Center GUI for CIMOMs discovered through SLP. For CIMOMs that are manually entered rather than discovered through SLP, check their provider’s documentation for the correct interop namespace. The following provider table of interop namespaces (Table 2-4 on page 67) reflects the namespaces at the time that this book was written.


Table 2-4 Interoperability namespace summary

Important: When providers release new versions of their products, these values can change. Check the provider’s documentation for that provider’s interop namespace.

Vendor Interoperability namespace

Cisco /root/cimv2.For version 3.2.1 or later:/root/pg_interop.

Brocade /interop or /root/brocade1.Note: Contact your switch vendor for the correct namespace to use.

McDATA /interop.

IBM /root/ibm.

Engenio /interop.

EMC /root/emc.

Hitachi For HiCommand 5.6 or higher, use: /root/smis/current.For a HiCommand version that supports SMI-S 1.2, use following namespace to traverse the model as SMI-S 1.1: /root/smis/smis11.For HiCommand versions lower than HiCommand 5.6, use /root/hitachi/dmxx, where xx is represents the level of HiCommand.

HP /root.

SUN StorEdge /root/sun3510 or /interop.Note: This is for a subsystem and not a switch.

IBM Tape /root/ibm.

XYRATEX /root/PG_interop.


2.10 Support

To get support for IBM TotalStorage Productivity Center for Data, you can contact IBM client support in one of the following ways:

� Go to the Data Manager technical support Web site found at the following address:

http://www.ibm.com/servers/storage/support/software/tpc/

� Clients in the United States can also call 1-800-IBM-SERV (1-800-426-7378).

� International clients need to consult the Web site for client support telephone numbers.

Note: To get online support, you must register your company and yourself. When you contact client support, be prepared to provide identification information for your company so that the support personnel can readily assist you. Company identification information might also be needed to access various online services available on the Web site.


http://www.ibm.com/servers/storage/support/software/tpc/

Chapter 3. Installing IBM TotalStorage Productivity Center for Data

This chapter describes the instructions for installing the IBM TotalStorage Productivity Center for Data and related components.

We intend for you to follow the instructions in this chapter in order to successfully install and set up a TotalStorage Productivity Center for Data environment for Windows, Linux, and AIX platforms.

Installing IBM TotalStorage Productivity Center for Data consists of the following tasks:

� Installing DB2� Installing the Agent Manager� Installing the Data Manager server� Installing the agent� Installing the Client User Interface

3


3.1 Installing TotalStorage Productivity Center

This section provides the step-by-step installation procedure for Total Storage Productivity Center for Data V3.3. Each marketing package (for example, TotalStorage Productivity Center for Data as opposed to TotalStorage Productivity Center Limited Edition) contains the complete TotalStorage Productivity Center product. The licenses that ship with each package limit the functions available at the graphical user interface (GUI) level.

When you install TotalStorage Productivity Center V3.3, the following installable components are available:

� Database schema� Data server� Device server� Graphical User Interface (GUI)� Command-Line Interface (CLI)� Data agent� Fabric agent

The CLI is considered optional. The Data agent and Fabric agents are likely to be installed in multiple locations. The GUI is installed wherever you want to control TotalStorage Productivity Center.

In this chapter, we show the installation for three environments; Windows Server 2003, Red Hat Linux, and AIX. The installation steps are similar for the last two environments, but the setup files to start the installation differ.

The default installation directory is:

� For Windows, c:\Program Files\IBM\... � For UNIX and Linux: /opt/IBM/...

You can change this path during the installation setup.

3.1.1 Installing Agent ManagerThe Agent Manager server is the computer system where the Agent Manager service and Agent Recovery Service run. Put the Agent Manager server on a server-class computer system that runs one of the supported operating systems.

Do not install the Agent Manager on the same computer system as an active Web server. If there is no other option, consider reconfiguring that Web server to release port 80 (by default, a Web server requires port 80).


The Agent Manager also requires this port to provide the Agent Recovery Service. This port conflict between the Agent Recovery Service and the Web server will prevent the Agent Manager from starting.

Registry information can only be put on a local DB2 Universal Database™, because TotalStorage Productivity Center V3.3 only supports an Agent Manager configured to run a local DB2 Database.

To estimate the size of the registry data, consider the following factors:

� The number of agents in your environment.

� How long the configuration data will be kept in the database.

� The length of rows in the agent tables. This number can vary depending on the type of columns. For example, a column that holds agent error information can be up to 2000 characters.

Use Table 3-1 to estimate the size of the registry for your environment.

Table 3-1 Estimated size of registry with varying numbers of agents

3.1.2 Installing Agent Manager on WindowsBefore you start the install, check that the following steps have been done:

� If the Agent Manager is already installed or being reinstalled because of a previous installation failure, you must uninstall the Agent Manager and remove its WebSphere configuration. Refer to the uninstall procedure found in IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.

� Check for port conflicts by issuing the following command:

netstat -an

Number of agents

Retain most recent only

Retain for seven days

Retain for 14 days

Average Rows

Max. Rows

Average Rows

Max. Rows

Average Rows

Max. Rows

100 55 Mb 70 Mb 69 Mb 91 Mb 86 Mb 115 Mb

1000 96 Mb 246 Mb 240 Mb 455 Mb 408 Mb 699 Mb

10000 511 Mb 2009 Mb 1951 Mb 4102 Mb 3631 Mb 6543 Mb

Chapter 3. Installing IBM TotalStorage Productivity Center for Data 71

The following ports must not be used by any other application. If there are port conflicts, you have to resolve them either by changing the other application’s port definitions or specifying other port numbers for Agent Manager. The ports that need to be reserved are:

50000 DB2 port

9511 Registration port

9512 Secure port

9513 Public port

9550 HTTP server port (GUI Web port)

� You have to use a user ID with the appropriate authority:

– For Windows, you must have administrative authority.

– For UNIX or Linux, you must have root authority.

� If the registry data will be in DB2 (local or remote), be sure that DB2 has already been installed. If it is not, the Agent Manager installation program will request that you point to the DB2 installation image in order to install DB2 before creating a registry entry in the database.

The default installation directory is:

� For Windows: c:\Program Files\IBM\...

� For UNIX or Linux: /opt/IBM/...

You can change this path during the installation setup. There are two types of installation of TotalStorage Productivity Center V3.3: typical and custom.

3.1.3 Typical installationThe Typical installation allows you to install all of the components of the TotalStorage Productivity Center V3.3 on the local server, by selecting the options Servers, Agents, and Clients. Our recommendation is to use the Custom installation, which gives you better control during the installation process.

3.1.4 Custom installationThe Custom installation allows you to install each component of the TotalStorage Productivity Center separately and to deploy remote Fabric and Data agents on multiple computers. This is the installation method that we recommend.


3.1.5 CD layout and componentsIn this section, we describe the contents of the product CDs at the time of the writing this book. This section is merely to give you an idea of the CD content. The media content differs depending on whether you use the Web images or the physical media that ships with the TotalStorage Productivity Center V3.3 package.

Passport Advantage and Web media contentThe Web media consists of three disk images:

� Disk1:

– OS: Windows, AIX, and Linux RH 3, and Linux RH4

– Database schema

– Data server

– Device server

– GUI

– CLI

– Local Data agent

– Local Fabric agent

� Disk2:

– OS: Windows, AIX, Linux RH 3, and Linux RH 4

– Remote installation of Data agent

– Remote installation of Fabric agent

– Java virtual machine (JVM™) for the Java Web Start Application for the Device server

� Disk3:

– OS: Windows, AIX, Linux RH 3, Linux RH 4, Linux Power, Linux s390 (Linux on System z), Solaris, and Hewlett Packard (HP)-UX

– Local Data agent

– Local Fabric agent

Note: When installing the TotalStorage Productivity Center server from Disk1, the installer will prompt you to insert Disk2 to copy files from it, and it will copy the remote installation files for Data agent and Fabric agent so that it can perform remote installations for those agents. If you only install local agents, you can use Disk3.


For information about the deployment of agents, refer to 4.1 “Agent deployment options” on page 288.

3.1.6 Configuration considerationsThis section provides examples of configuring the TotalStorage Productivity Center V3.3 components.

There are two most likely configurations, and both of these configurations are supported: a one server environment and a two server environment. In a two server environment, you can only separate Agent Manager from the TotalStorage Productivity Center V3.3 server, because the Data server and Device server have to be installed on the same machine.

One server environmentIn this environment, all of the components are installed on one server:

� DB2� Agent Manager� Data server� Device server� CLI� GUI

Two server environmentIn a two server environment, you install the components in the following manner. Note that you can have DB2 on a remote server. The components are:

� Server 1:

– DB2– Agent Manager

� Server 2:

– DB2– Data server– Device server– GUI– CLI


3.2 Pre-installation steps for Windows

The prerequisite components for IBM TotalStorage Productivity Center V3.3 on Windows are:

� IBM DB2 UDB Enterprise Server Edition V8.1 Fix Pack 14 or higher

� Agent Manager V1.3.2 or higher

The component installation orderInstall the components in the following order:

1. DB22. Data Manager3. TotalStorage Productivity Center components

3.2.1 Verify the primary domain name systems Before you start your installation, we recommend that you verify if a primary domain name system (DNS) suffix is set, if your server has a static IP address, and if this address is resolved to the fully qualified name by using the nslookup command. Setting up a DNS might require a computer restart.

Tip: We recommend that you install the database schema first, then install the Data server and the Device server in a separate step.

If you install all of the components in one step, if any part of the installation fails for any reason (for example, insufficient space or incorrect passwords), the installation suspends and rolls back, uninstalling all of the previously installed components.


To verify the primary DNS name, follow these steps:

1. Right-click the My Computer icon on your desktop.

2. Click Properties.

3. The System Properties window is displayed, as shown in Figure 3-1.

4. On the Computer Name tab, click Change.

Figure 3-1 System properties

5. Enter the host name in the Computer name field. Click More to continue (Figure 3-2 on page 77).


Figure 3-2 Computer name

6. In the next window, verify that the Primary DNS suffix of this computer field displays a domain name. Click OK (Figure 3-3).

Figure 3-3 DNS domain name

7. If you made any changes, you might need to restart your computer (Figure 3-4).

Figure 3-4 You must restart


3.2.2 Activate NetBIOS settingsIf NetBIOS is not enabled on Windows Server 2003, the Globally Unique Identifier (GUID) does not get generated. You need to verify and activate the NetBIOS settings:

1. On your TotalStorage Productivity Center server, select Start → Settings → Network and Dial-up Connections. Select your Local Area Connections. From the Local Area Connection Properties window, double-click Internet Protocol (TCP/IP). The next window is the Internet Protocol (TCP/IP) Properties window. Click Advanced, as shown in Figure 3-5.

Figure 3-5 TPC/IP properties

2. Then, select the WINS tab, select Enable NetBIOS over TCP/IP, and click OK (Figure 3-6 on page 79).


Figure 3-6 Advanced TCP/IP properties

3.2.3 Using and defining user IDs and passwordsIn this section, we describe the user IDs and passwords that you need to define or set up during the TotalStorage Productivity Center installation.

Valid characters for user ID and password fieldsThere are rules for the user IDs and passwords that are used for TotalStorage Productivity Center.

For a Typical installationThe user IDs and passwords that you need for a Typical installation are:

� Common user IDs and passwords (DB2 Administrator/User, WebSphere Application Server Administrator, Host Authentication, Common agent Windows Service, and network-attached storage (NAS) Filer) must contain characters from the following categories:

– Uppercase characters: A through Z

– Lowercase characters: a through z

– Numeric characters: 0 through 9

– Non-alphanumeric characters: - _ .


� Common agent Registration Password or Resource Manager Registration user ID and password must contain characters from the following categories:




– Non-alphanumeric characters: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < > / ?

For a Custom installationThe user IDs and passwords that you need for a Custom installation are:

� The DB2 Administrator user ID and password or DB2 user ID and password must contain characters from the following categories:




– Non-alphanumeric characters: ~ @ # % ^ & ( ) - _ { } .

� The WebSphere Application Server user ID and password or Host Authentication password must contain characters from the following categories:




– Non-alphanumeric characters: - _ .

� The Common agent Windows Service user ID or NAS Filer user ID must contain characters from the following categories:




– Non-alphanumeric characters: ` ~ # % ^ & ( ) - _ { } ' .

� The Common agent Windows Service password or NAS Filer password must contain characters from the following categories:






� The Common agent Registration password or Resource Manager Registration user ID and password must contain characters from the following categories:





User IDs and passwords created during installation

Table 3-2 through Table 3-12 on page 87 contain information about the user IDs and passwords that are used during the installation of the TotalStorage Productivity Center prerequisites and components.

Table 3-2 Installing DB2 and Agent Manager

Item OS Description Created when Used when

Installing DB2 and Agent Manager

All Log on Windows as a local Administrator.

N/A. Used to log on Windows to install DB2 and Agent Manager.

Group User ID Password ITSO’s user ID and password

Administrator User ID used to log on.

Used to log on. Administrator/ password.


Table 3-3 Installing Device server or Data server

Item OS Description Created when

Used when

Installing Device server or Data server

All Add user ID to DB2 Admin group or assign the user rights: � Log on as a

service. � Act as part of the

operating system. � Adjust memory

quotas for a process.

� Create a token object.

� Debug programs. � Replace a process

level token. On Linux or UNIX, give root authority.

Must be created before starting the Device server and Data server installation.

Used to log on to Windows to install Device server and Data server.


Administrator New user ID used to log on to Windows.

New password used to log on Windows.

tpcadmin/ tpcadmin.


Table 3-4 Installing Data agent or Fabric agent

To install a GUI or CLI, you do not need any particular authority or special user ID (Table 3-5).

Table 3-5 DB2 administration server


Installing Data agent or Fabric agent

All User rights:� Act as part of

the operating system.

� Log on as a service.

On Linux or UNIX, give root authority.

Has to be created before starting the Data agent or Fabric agent installation.

Used to log on to Windows to install Data agent or Fabric agent.


Administrator New user ID used to log on to Windows.

New password used to log on to Windows.

tpcadmin/ tpcadmin.


DB2 administration server user

All Used to run the DB2 administration server on your system. Used by the DB2 GUI tools to perform administration tasks. See the rules in “DB2 user ID and password rules”.

Specified when DB2 is installed.

Used by the DB2 GUI tools to perform administration tasks.


New user ID. New password. db2tpc/db2tpc.


DB2 user ID and password rulesDB2 user IDs and passwords must follow these rules:

� UNIX user names and passwords cannot be more than eight characters long. They cannot start with a numeric digit or end with the dollar sign character ($).

� Windows 32-bit user IDs and passwords can contain one to 20 characters.

� Group and instance names can contain one to eight characters.

� User IDs cannot be:

– USERS – ADMINS – GUESTS – PUBLIC – LOCAL

� User IDs cannot begin with:

– IBM – SQL – SYS

� User IDs cannot include accented characters.

� UNIX users, groups, and instance names must be lowercase.

� Windows 32-bit users, groups, or instance names can be any case.

DB2 creates a user group with the following administrative rights:

� Acts as a part of an operating system.� Creates a token object.� Increases quotas.� Replaces a process-level token.� Logs on as a service.

Note: Adding the user ID used to install TotalStorage Productivity Center to the DB2 Admin group gives the user ID the necessary administrative rights.


Table 3-6 Certificate authority password

Table 3-7 Common agent registration passwords


Certificate authority password

All This password locks the CARootKeyRing.jks file. Specifying a value for this password is optional. You need to specify this password only if you want to be able to unlock the certificate authority files. We recommend that you create a password.

Specified when you install Agent Manager.

You need to specify the value for the certificate authority password only if you need to open the truststore files to examine the certificates that they contain.

group User ID Password ITSO’s user ID and password

N/A N/A No default. If not specified, a password is generated automatically.

tpctpc.

Important: Do not change the agent registration password under any circumstances. Changing this password will render the certificates unusable.


Common agent registration

All. This is the password required by the Common agent to register with the Agent Manager.

Specified when you install Agent Manager.

Used during Common agent, Data agent, and Fabric agent installation.


N/A. N/A. changeMe (the default).

changeMe.


Table 3-8 Common agent service logon user ID and password

Table 3-9 Host authentication password

Table 3-10 NAS filer login user ID and password


Common agent service logon user ID and password

Windows. This creates a new service account under which the Common agent runs.

Specified when you install Data agent or Fabric agent (only local).

N/A.


Admini-strators.

If you do not specify anything, itcauser is created by default.

N/A. tpcadmin/ tpcadmin.


Host authentication password

All. N/A. Specified when you install the Device server.

Used when you install Fabric agent to communicate with the Device server.


N/A. N/A. Must be provided.

tpctpc.


NAS filer login user ID and password

Windows. N/A. Specified when you run NAS discovery.

N/A.


N/A. N/A. N/A. N/A.


Table 3-11 Resource manager registration user ID and password

Table 3-12 WebSphere Application Server administrator user ID and password

3.3 Windows installationThis section describes the installation of TotalStorage Productivity Center in a Windows environment.

3.3.1 DB2 installation for WindowsIn this section, we show a Typical installation of DB2 Version 9.1. DB2 must be installed before you install Agent Manager and IBM TotalStorage Productivity Center. Before beginning the installation, it is important that you log on to your system as a local administrator with Administrator authority for Windows or root authority for UNIX and Linux (Table 3-2 on page 81).


Resource manager registration user ID and password

All. N/A. Specified when you install Device server and Data server.

Used when Device server and Data server have to register to Agent Manager.


N/A. manager(by default).

password(by default).

manager/ password.


WebSphere Application Server administrator user ID and password

All. You can use tpcadmin in order to avoid creating a new user ID and password.

Specified when you install Device server.

Used when Device server has to communicate with WebSphere.


N/A. If not provided, it will be created.

if not provided, it will be created.

tpcadmin/ tpcadmin.


To begin the installation of DB2, follow these steps:

1. Insert the IBM TotalStorage Productivity Center Prerequisite Software Installer CD into the CD-ROM drive.

2. If Windows autorun is enabled, the installation program starts automatically. If it does not, open Windows Explorer and go to the IBM TotalStorage Productivity Center CD-ROM drive. Go to the DB2 Installation image path and double-click setup.exe. You will see the first window, as shown in Figure 3-7. Select Install Product to proceed with the installation.

Figure 3-7 DB2 Setup welcome window

3. The next window allows you to select the DB2 product to be installed. Click Install New to proceed, as shown in Figure 3-8 on page 89.

Note: TotalStorage Productivity Center V3.3 requires DB2 Version 8.1.14 (includes Fix Pack 14) or higher.


Figure 3-8 Select product

The InstallShield Wizard starts (Figure 3-9).

Figure 3-9 Preparing to install


4. The DB2 Setup wizard window is displayed, as shown in Figure 3-10. Click Next to proceed.

Figure 3-10 Setup wizard


5. You have to click I accept the terms in the license agreement if you accept the terms (Figure 3-11).

Figure 3-11 License agreement


6. To select the installation type, accept the default of Typical and click Next to continue (Figure 3-12).

Figure 3-12 Typical installation


7. Accept the defaults and select Install DB2 Enterprise Server Edition on this computer (Figure 3-13). Click Next to continue.

Figure 3-13 Installation action


8. The window shown in Figure 3-14 shows the drive and the directory to be used as the installation folder. Click Next to continue.

Figure 3-14 Installation folder

9. Set the user information for the DB2 Administration Server; choose the domain of this user. If it is a local user, leave the field blank.

Note: The default drive for the DB2 installation on the Windows platform is C: and the default path is \Program Files\IBM\SQLLIB\. At this point, you can change the defaults as we did or accept the default configuration.


10.Type a user name and password of the DB2 user account that you want to create (Figure 3-15). You can refer to Table 3-5 on page 83.

DB2 creates a user on your system with the following administrative rights:

– Act as a part of an operating system.– Create a token object.– Increase quotas.– Replace a process-level token.– Log on as a service.

Figure 3-15 User Information


11.In the Configure DB2 instances window, accept the default and click Next to continue (Figure 3-16).

Figure 3-16 Configure DB2 instances


12.Accept the defaults, as shown in Figure 3-17. Verify that Prepare the DB2 tools catalog on this computer is not checked. Click Next to continue.

Figure 3-17 Prepare DB2 tools catalog


In the window shown in Figure 3-18, verify that Set up your DB2 server to send notifications is not checked and then click Next to continue. In our installation, we uncheck it. If notification is required in your environment, you can enable it.

Figure 3-18 Set up notifications


13.In the window shown in Figure 3-19, verify Enable operating system security is checked, confirm that the DB2 administrator group is set as DB2ADMNS, and the DB2 users group is set as DB2USERS. Click Next to continue.

Figure 3-19 Enable operating system security


14.The window shown in Figure 3-20 is presented. Click Install to continue.

Figure 3-20 Start copying files


The DB2 installation proceeds and you see a progress window similar to the one shown in Figure 3-21.

Figure 3-21 Installing DB2 Enterprise Server Edition installation progress


15.When the installation completes, click Finish, as shown in Figure 3-22.

Figure 3-22 DB2 Setup wizard completion window

16.Click Exit First Steps (Figure 3-23 on page 103) to complete the installation.


Figure 3-23 Universal Database First Steps window

Verifying the installation 1. To verify the DB2 installation, check if the db2tpc user has been created and

included in the DB2ADMNS group.


2. Open a Command Prompt window and enter the db2level command to check the version installed, as shown in Figure 3-24.

Figure 3-24 The db2level command

Figure 3-25 on page 105 shows the DB2 Windows Services that were created at the end of the installation.


Figure 3-25 Windows Services showing DB2 services

3.3.2 Agent Manager installation This is a Typical installation of Agent Manager V1.3.2.26.

When you install the Agent Manager, you also install the Embedded version of IBM WebSphere Application Server - Express, V6.0.2 (WebSphere Express).

To install the Agent Manager, follow these procedures:

1. Run the following program from the Embedded Installer directory (Table 3-13). You must have Java virtual machine (JVM) installed. If you want to designate an alternate path to the JVM, use the command in the third column in Table 3-13.

Table 3-13 Embedded Installer directory commands

Operating system Command Java error failure alternate command

Microsoft Windows setupwin32.exe setupwin32.exe -is:javahome ..\jre\windows


2. The InstallShield Wizard starts, and you see a window similar to the one shown in Figure 3-26.

Figure 3-26 InstallShield Wizard window

AIX setupAix.bin setupAix.bin -is:javahome ../

Linux setupLinux.bin setupLinux.bin -is:javahome ../

Linux on Power PC setupLinuxPPC.bin setupLinux.bin -is:javahome ../

Solaris setupSolaris.bin setupLinux.bin -is:javahome ../

Important: Log on with a user ID that has administrative authority on Windows and root authority on UNIX or Linux.

Operating system Command Java error failure alternate command


3. The “Choose the runtime container for the Agent Manager” window appears, as shown in Figure 3-27, with the default option The WebSphere Application Server. Make sure that the WebSphere Application Server is already installed already selected. Do not select this option, because we do not have WebSphere installed. Instead, choose The embedded version of the IBM WebSphere Application Server delivered with the Agent Manager installer, and click Next to continue.

Figure 3-27 Agent Manager installation window


4. Figure 3-28 shows the Directory Name for the installation. Click Next to accept the default or click Browse to install Agent Manager in another directory. In our installation, we install Agent Manager in the default directory.

Figure 3-28 Directory Name window

Note: The default directory name for Agent Manager is C:\Program Files\IBM\AgentManager\.


5. The Type and Location of Registry window is displayed, as shown in Figure 3-29. Choose DB2 database on this computer, which is the default, and click Next to continue.

Figure 3-29 Type and Location of Registry window


6. In the next DB2 Universal Database Connection Information window, which is shown in Figure 3-30, enter the following database information:

– Database Software Directory

Enter the directory where DB2 is installed on your system. In our case, the default installation directory for DB2 was selected, which is C:\Program Files\IBM\SQLLIB\.

– Database Name

A default database called IBMCDB will be created for the Agent Manager.

After entering the information, click Next to continue.

Figure 3-30 DB2 Universal Database Connection Information window

7. The Database User Information window is shown as Figure 3-31 on page 111. Enter the database user name and password. For these fields, use the DB2 administrator user ID that is in the DB2ADMNS group and the Administrator group (Figure 3-19 on page 99). If you want to use another user ID for the installation of Agent Manager, you can select Use a different user ID during the installation, and enter the user ID and password that you


want. However, note that if you do not select the check box, the following Database Administrator user ID and password will not be used.

We recommend that you use the DB2 user ID and password from the DB2 installation if you use DB2 only for TotalStorage Productivity Center. You can refer to Table 3-5 on page 83 for the DB2 user ID and password. In our installation, we use the DB2 user ID and password from the DB2 installation. Click Next to continue.

Figure 3-31 Database User Information window

8. The WebSphere Application Server Connection Information window is shown in Figure 3-32 on page 113. Enter the following information, and click Next to continue:

– Host Name or Alias of Agent Manager

Review the preinstallation task that is mentioned in 3.2.1 “Verify the primary domain name systems” on page 75. Use the fully qualified host name. For example, specify lead.itsosj.sanjose.ibm.com. This value is used for the URLs for all Agent Manager services. It is preferable to use the fully qualified host name rather than an IP address.


If you specify an IP address, you will see the warning window shown in Figure 3-33 on page 114.

– Registration Port

Use the default port of 9511 for the server-side Secure Sockets Layer (SSL).

– Secure Port

Use the default port of 9512 for client authentication and two-way SSL.

– Public Port and Alternate Port for the Agent Recovery Service

Use the public communication port default of 9513.

– Do not use port 80 for the Agent Recovery Service.

Accept the default and do not check this box. If you check this box, make sure that port 80 is not being used by another application. To check for other applications that use port 80, run this command:

netstat -an


Figure 3-32 WebSphere Application Server Connection Information window

Note: If you want Agent Recovery Service to run, you must stop any service using port 80. If any service is using port 80, Agent Recovery Service installs, but does not start.


9. If you specify an IP address instead of a fully qualified host name for the Host Name or Alias of Agent Manager, you see the warning window that is shown in Figure 3-33. We recommend that you click Back and specify a fully qualified host name.

Figure 3-33 Warning window that you get if an IP address is specified


10.In the WebSphere Application Server Connection Information window that is shown in Figure 3-34, accept the defaults and click Next to continue.

Figure 3-34 WebSphere Application Server Connection Information window


11.In the Security Certificates window (Figure 3-35), we highly recommend that you accept the defaults to generate new certificates for a secure environment.

Click Next to continue.

Figure 3-35 Create security certificates

12.In the window that is shown in Figure 3-36 on page 117, specify the Security Certificate settings. To create certificates, you must specify a certificate authority password. You must specify this password in order to be able to look at the certificate files after they are generated.

After entering the password and confirming the password, click Next to continue.


Figure 3-36 Define the Certificate Authority window

13.In the Agent Manager Set Passwords window that is shown in Figure 3-37 on page 118, enter the following information and click Next to continue:

– Agent Manager Password

This password is the resource manager registration password. This password is used to register the Data server or Device server with the Agent Manager. Enter the password twice.

Note: The Agent Manager V1.2 installer provided a default user ID and password as manager and password. For Agent Manager V1.3.2, there is no default password.

At the time of the writing of this book, entering a password other than “password” will cause the Data server and Device server installations to fail. Check the TotalStorage Productivity Center flashes to verify whether this situation has been fixed before entering a password other than “password”.


– Agent Registration Password

This password is used to register the Common agents (for Fabric agent and Data agent). You must supply this password when you install the agents. This password locks the agentTrust.jks file. Enter the password twice.

You must provide a password here; otherwise, you cannot continue the installation process.

Figure 3-37 Agent Manager Set Passwords window

Note: The Agent Manager V1.2 installer provided a default password of changeMe. For Agent Manager 1.3.2, there is no default password.


14.The User Input Summary window is displayed (Figure 3-38). If you want to change any settings, click Back and return to the window where you set the value. If you do not need to make any changes, click Next to continue.

Figure 3-38 Input summary


15.The next window is the embedded WebSphere Application Server installation window, which is shown in Figure 3-39. This installation takes a while, so be patient.

Figure 3-39 WebSphere Application Server installation window

16.When the WebSphere Application Server installation completes, you see the summary information window. Review the summary information window (Figure 3-40 on page 121) and click Next to continue.


Figure 3-40 Summary information window

The Agent Manager installation starts and you see several messages indicating the installation process. This normally takes about five minutes.


17.The next window you see shows the process checking the status of WebSphere running applications (Figure 3-41). Click Next to continue.

Figure 3-41 Checking the status of the running WebSphere applications


18.The Start the AgentManager Application Server window is shown in Figure 3-42. Choose Yes, start AgentManager now, and click Next to continue.

Figure 3-42 Start the AgentManager Application Server


19.Next, you see the window shown in Figure 3-43, which indicates that the WebSphere server is starting the Agent Manager.

Figure 3-43 Starting WebSphere server AgentManager


20.The Summary of Installation and Configuration Results window is displayed in Figure 3-44. Verify that the Agent Manager has successfully installed all of its components. Review the window and click Next to continue.

Figure 3-44 Summary of Agent Manager installation and configuration


21.The last window (Figure 3-45) shows that the Agent Manager has been successfully installed. Click Finish to complete the Agent Manager installation.

Figure 3-45 Finish the Agent Manager installation

Verifying the installationYou can verify the installation by running the HealthCheck utility from a command prompt.

From the command prompt, first navigate to the <InstallDir>\IBM\AgentManager\toolkit\bin directory and run HealthCheck. To understand how to use HealthCheck, refer to the HealthCheck.readme file, which is located in the <InstallDir>\IBM\AgentManager\toolkit directory.

In our installation, we used the passw0rd password (with zero) as the Agent Registration password, so we specify it as part of the RegistrationPW parameter. Refer to Figure 3-46 on page 127.


Figure 3-46 HealthCheck utility result

In Figure 3-47, verify that the ARS.version field shows the level that you have installed (in our case, it is 1.3.2.26). Confirm that you have received the message Health Check passed at the end of the HealthCheck utility listing, as shown in Figure 3-47.

Figure 3-47 HealthCheck utility result


After the completion of the Agent Manager installation, you can verify if the database was created (Figure 3-48). Enter db2cmd from a command prompt and press Enter. The db2 Command Line Processor window opens. Enter db2 and press Enter, then enter the list database directory database manager command.

Figure 3-48 DB2 command line list of the database directory

Then, if the database exists, you can verify the connection to the database (Figure 3-49). From the db2 Command Line Processor, enter the command connect to IBMCDB user db2tpc using itsodb2.

Figure 3-49 DB2 command line connect to database


3.3.3 Install TotalStorage Productivity Center components Now that the prerequisites have been installed, we install the TotalStorage Productivity Center components:

1. Before starting the installation, verify that DB2 V9.1 Enterprise Edition has been installed (Figure 3-24 on page 104) and has been started (Figure 3-50).

Figure 3-50 DB2 command line db2stat

2. For Windows, if Windows autorun is enabled, the installation program starts automatically. If it does not, open Windows Explorer and go to the TotalStorage Productivity Center CD-ROM drive or directory. Double-click setup.exe.

Important: For Windows, log on to your system as a local administrator with database authority.


3. Choose your language and click OK (Figure 3-51).

Figure 3-51 Language selection window

4. The License Agreement window is displayed. Read the terms and then selectI accept the terms of the license agreement, if you agree with them. Click Next to continue (Figure 3-52).

Figure 3-52 License Agreement window

5. Figure 3-53 on page 131 shows how to select a Typical or Custom installation. You have the following options:

– Typical installation allows you to install all of the components on the same computer by selecting Servers, Agents, and Clients.


– Custom installation allows you to install each component separately.

– Installation licenses

This selection installs the TotalStorage Productivity Center licenses. The TotalStorage Productivity Center license is on the CD. You only need to run this option when you add a license to a TotalStorage Productivity Center package that has already been installed on your system. For example, if you have installed the TotalStorage Productivity Center for Data package, the license will be installed automatically when you install the product. If you decide to later enable TotalStorage Productivity Center for Fabric, run the installer and select Installation licenses. This option will allow you to install the license key from the CD. You do not have to install the IBM TotalStorage Productivity Center for Fabric product.

In this chapter, we document the Custom Installation. Click Next to continue.

Figure 3-53 Custom installation


6. In the Custom installation, you can select all of the components in the window that is shown in Figure 3-54, which is the recommended installation scenario. In our scenario, we show the installation in stages. By default, all components (except the Remote Data agent and the Remote Fabric agent) are checked. As the first step, we only select the option Create database schema, and then we click Next to proceed (Figure 3-54).

Figure 3-54 Custom installation component selection


7. To start the Database creation, you must specify a DB2 user ID. We suggest that you use the same DB2 user ID that you created when you installed DB2 (Table 3-5 on page 83). Click Next, as shown in Figure 3-55.

Figure 3-55 DB2 user and password


8. Enter your DB2 user ID and password again (Table 3-5 on page 83). Do not use the default of Use Local Database. Click Create local database. By default, a database named TPCDB is created. Click Schema creation details to continue (Figure 3-56).

Figure 3-56 DB2 user ID and create local database window

The window shown in Figure 3-57 on page 135 allows you to change the default space assigned to the database. Review the defaults and make any changes. In our installation, we accepted the defaults.

For better performance, we recommend that you:

– Allocate TEMP DB on another physical disk than the physical disk that contains the TotalStorage Productivity Center components.

– Create larger Key and Big databases.

Select System managed (SMS), click OK, and then, click Next to proceed (Figure 3-57 on page 135).


Figure 3-57 DB2 schema space

Note: We recommend that you select System managed (SMS). To understand the advantage of an SMS database as compared to a DMS database, refer to the section “Selecting an SMS or DMS tablespace”, in IBM TotalStorage Productivity Center V3.1: The Next Generation, SG24-7194.


9. Next, you see the summary information about the TotalStorage Productivity Center installation that you have selected, as shown in Figure 3-58. Click Install to continue.

Figure 3-58 TotalStorage Productivity Center installation information


10.The next window shows that the TotalStorage Productivity Center has been successfully installed (Figure 3-59). Click Finish to exit the InstallShield Wizard.

Figure 3-59 Installation summary information


Verifying the installationTo check the installation, select Start → All Programs → IBM DB2 → DB2COPY1 → General Administration Tools → Control Center to start DB2 Control Center in order to verify that you have two DB2 databases in your environment (as shown in Figure 3-60).

Figure 3-60 Verifying the DB2 installation

Log filesCheck for errors and Java exceptions in the log files at the following locations:

� <InstallLocation>\TPC.log� <InstallLocation>\log\dbSchema\install\dbSchemaInstallIS.log

For Windows, the default InstallLocation is c:\Program Files\IBM\TPC.

Check for the success message at the end of the log files to verify a successful installation.

Important: Do not edit or modify anything in DB2 Control Center. Modifying this information can cause serious damage to your tablespace. Simply use DB2 Control Center to browse your configuration.


3.3.4 Installing the Data server, Device server, GUI, and CLIIn our environment, we performed a custom installation of the Data server, Device server, GUI, and CLI.

Preinstallation tasksTo install Data server and Device server components, you must log on to Windows Server 2003 with a user ID that has the following rights:

� Log on as a service.� Act as part of the operating system.� Adjust memory quotas for a process.� Create a token object.� Debug programs.� Replace a process-level token.

Be certain that the following tasks are completed:

� We recommend that you create a user ID for installation. We created the user ID tpcadmin (refer to Table 3-3 on page 82).

� The database schema must be installed successfully to start the Data server installation.

� An accessible Agent Manager must be available to start the Device server installation.

� Data server must be successfully installed prior to installing the GUI.

� Device server must be successfully installed prior to installing the CLI.

Custom installationTo perform a custom installation, follow these steps:

1. Start the TotalStorage Productivity Center installer.

2. Choose the language to be used for installation.

3. Accept the terms of the License Agreement.

4. Select the Custom Installation.


5. Select the components that you want to install. In our scenario, we select the four server components, as shown in Figure 3-61. Note that the option, Create database schema, is grayed out and the option, Register with the agent manager, is selected.

Figure 3-61 Installation selection


6. In the Database administrator information window, which is shown in Figure 3-62, the DB2 user ID and password already shows in the user ID and password fields, because we used them to create the database schema. Click Next.

Figure 3-62 User ID and password


7. In the existing database schema information window, click Use local database. We will use the database TPCDB that we just created in the previous step. Click Next to continue (Figure 3-63).

Figure 3-63 Selecting the local database

8. In the window shown in Figure 3-64 on page 144, enter the following information:

– Data server name

Enter the fully qualified host name of the Data server.

– Data server port

Enter the Data server port. The default is 9549.

– Device server name

Enter the fully qualified host name of the Device server.

– Device server port

Enter the Device server port. The default is 9550.

– TPC Superuser

Enter the Administrators Group for the TPC Superuser. We created the user ID tpcadmin and added this user ID to the existing Administrators


group. See 3.2.3 “Using and defining user IDs and passwords” on page 79 for more details.

– Host authentication password

This is the password used for the Fabric agents to communicate with the Device server. Remember to record this password. See Table 3-4 on page 83.

– Data server account password

For Windows only. TotalStorage Productivity Center installer will create an ID called TSRMsrv1 with the password that you specified here to run the Data server service. The display name for the Data server in Windows Services window is:

IBM TotalStorage Productivity Center - Data Server

– WebSphere Application Server admin ID and password

This is the user ID and password required by the Device server to communicate with the embedded WebSphere Application Server.

You can use the TPC Superuser here. In our case, we used tpcadmin. Refer to Table 3-3 on page 82 for further details.

If you click Security roles, the Advanced security roles mapping window is displayed. You can assign a Windows OS group to a role group for each TotalStorage Productivity Center role with which you want to make an association, so we can have multiple authority user IDs to perform various TotalStorage Productivity Center operations. The operating group must exist before you can associate a TotalStorage Productivity Center role with a group. You do not have to assign security roles at installation time; you can assign these roles after you have installed TotalStorage Productivity Center.

If you click NAS discovery, the NAS discovery information window is displayed. You can enter the NAS filer login default user name and password and the SNMP communities to be used for NAS discovery. You do not have to assign the NAS discovery information at installation time; you can configure it after you have installed TotalStorage Productivity Center. Refer to 4.9.1 “Manual NAS/NetWare server entry” on page 345 for details.



Figure 3-64 Component information for installation

9. In the next window, shown in Figure 3-65 on page 145, enter the Agent Manager information. You must specify the following information:

– Host name or IP address

Fully qualified name or IP address of the Agent Manager server. For further details about the fully qualified name, refer to 3.2.1 “Verify the primary domain name systems” on page 75.

– Port (Secured)

Port number of the Agent Manager server. If acceptable (this port is not in use by any other application), use the default port 9511.

– Port (Public)

The public communication port. If acceptable (this port is not in use by any other application), use the default port of 9513.

– User ID

This is the user ID that is used to register the Data server or Device server with the Agent Manager. You have to use the built-in user ID “manager”, because it cannot be specified during the Agent Manager V1.3.2.26 installation (Figure 3-65 on page 145).


– Password

This password is used to register the Data server or Device server with the Agent Manager. You previously specified this user ID during the Agent Manager installation (refer to Figure 3-37 on page 118). The default is password.

– Password - Common agent registration password

This password is used by the Common agent to register with the Agent Manager. It was specified when you installed the Agent Manager (refer to Figure 3-36 on page 117). This password can be verified using the HealthCheck utility found under the <InstallDir>\IBM\AgentManager\toolkit\bin directory.


Figure 3-65 Agent Manager information


10.The Summary information window is displayed. Review the information, and then click Install to continue (Figure 3-66).

Figure 3-66 Summary of installation


The installation starts. You might see several messages that are related to the Data server installation, which are similar to Figure 3-67.

Figure 3-67 Installing Data server


11.If you install from the electronic image, the installer prompts you to change to the directory of the second disk (Figure 3-68). Click Browse and choose the directory of Disk2, and click OK to continue.

Figure 3-68 Multiple disk installation window

Tip: If you extract the files from Disk1 and Disk2 into a directory with the names disk1 and disk2, the TotalStorage Productivity Center installation program can find the Disk2 files, and it does not show the Insert Next Disk window (Figure 3-68 on page 148). Put Disk1 and Disk2 in the same directory, for example, on Windows (note that this is case-sensitive):

C:\disk1 C:\disk2

or

C:\tpc33\disk1 C:\tpc33\disk2


12.At the end of the installation, you see the summary information window (Figure 3-69). Read and verify the information. Click Finish to complete the installation.

Figure 3-69 Component installation completion window


Verifying the installationAt the end of the installation, the Windows Services shows that the Data server and Device server services (shown in Figure 3-70) have been installed.

Figure 3-70 Windows Services

Log files for the Data serverCheck the logs for any errors or Java exceptions. The log files for the Data server are:

� <InstallLocation>\TPC.log� <InstallLocation>\log\data\install� <InstallLocation>\log\install� <InstallLocation>\data\log

For Windows, the default InstallLocation is C:\Program Files\IBM\TPC.

Log files for the Device serverCheck the log files for any errors. The log files for the Device server are:

� <InstallLocation>\TPC.log� <InstallLocation>\log\device\install� <InstallLocation>\device\log



Log files for GUICheck the log files for any errors. The log files for the GUI are:

� <InstallLocation>\TPC.log� <InstallLocation>\log\gui\install� <InstallLocation>\gui\log


Log files for CLICheck the log files for any errors. The log files for the CLI are:

� <InstallLocation>\TPC.log� <InstallLocation>\log\cli\install


3.4 Linux installationThis section describes the installation of TotalStorage Productivity Center for Data V3.3 in a Linux (in our installation, we used Red Hat Enterprise Linux AS Release 5 update 2 distribution) environment.

Assuming that you have not installed DB2 yet and you do not want to use a remote DB2 instance, you have to start with the installation of IBM DB2. After that, you need to install the Agent Manager. Finally, you can install the TotalStorage Productivity Center Data server and Device server, the GUI, and the CLI.

3.4.1 Installing DB2 Version 9 on a Linux platform

First, you need to access your DB2 installation media. You can install DB2 by using the graphical installer. To install DB2 by using the graphical installer, run db2setup. As an alternative, you can use the command-line installer by running db2_install, which only installs the DB2 data to your operating system. You still need to configure DB2 manually. Using the graphical installer to install DB2, you have three options to select the type of installation that you want. These options are Typical, Compact, and Custom. We describe the Custom option to install DB2.


Follow these steps to perform the installation of IBM DB2 UDB:

1. At the command prompt, enter the following command to start the installation:

./db2setup

The IBM DB2 Setup launchpad opens (Figure 3-71).

Figure 3-71 DB2 Setup launchpad


2. The product selection window appears, as shown in Figure 3-72. Choose DB2 UDB Enterprise Server Edition and click Install New.

Figure 3-72 DB2 Setup launchpad product selection


3. The DB2 Setup wizard is loaded (see Figure 3-73).

Figure 3-73 DB2 Setup wizard: Welcome window


4. The Software License Agreement is displayed (Figure 3-74). If you agree with the software license agreement, select Accept and click Next. If you do not accept the license agreement, you cannot continue with the installation.

Figure 3-74 DB2 Setup wizard: Software License Agreement


5. The Select the installation type window appears (Figure 3-75).

Figure 3-75 DB2 Setup wizard: Installation type


6. We suggest that you select the Typical installation option, which provides you with the most straightforward installation process. Select Typical and then click Next. The installation action window is displayed (Figure 3-76). Select Install DB2 UDB Enterprise Server Edition on this computer and save my settings in a response file.

Figure 3-76 DB2 Setup wizard: Installation action


7. Select the installation directory where you want to install DB2. Click Next to continue (Figure 3-77).

Figure 3-77 Select the installation directory window

8. The DB2 Administration Server (DAS) user window appears (Figure 3-78 on page 159).


Figure 3-78 DB2 Setup wizard: DB2 Administration Server user information

9. If you want the installer to create a DB2 Administration Server user ID, you must enter a unique user name for the DAS user in the user name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank and check Use default UID and Use Default GID, the system assigns a UID and a GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the DAS user. After you have completed this panel, click Next.


The Set up a DB2 instance window will display (Figure 3-79).

Figure 3-79 DB2 Setup wizard: DB2 instance setup


10.Select Create a DB2 instance and click Next. The instance partitioning window appears (Figure 3-80).

Figure 3-80 DB2 Setup wizard: Instance type


11.Select Single-partition instance and click Next. The DB2 instance owner window appears (Figure 3-81).

Figure 3-81 Setup wizard: Instance owner user information window


12.If you want the installer to create a DB2 instance owner user ID, you must enter a unique user name for the instance owner in the user name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank and check Use default UID and Use default GID, the system will assign a UID and a GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the instance owner. After you have completed this window, click Next. The Set user information for the fenced user window will display (Figure 3-82).

Figure 3-82 DB2 Setup wizard: Fenced user information window


13.If you want the installer to create a DB2 fenced user ID, you must enter a unique user name for the fenced user in the user name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank and check Use default UID and Use default GID, the system will assign a UID and a GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the fenced user. After you have completed this window, click Next. The Prepare the DB2 tools catalog window will display (Figure 3-83).

Figure 3-83 DB2 Setup wizard: DB2 tools catalog window

14.Click Do not prepare the DB2 tools catalog on this computer, and then click Next. The Set up the administration contact window appears (Figure 3-84 on page 165).


Figure 3-84 DB2 Setup wizard: Administration contact list window

15.If you do not have another DB2 server in your environment with an existing contact list, choose the default option of Local - Create a contact list on this system and click Next (Figure 3-84). If you do not enable the Simple Mail Transfer Protocol (SMTP) notification, you will receive a warning message. Click OK to the warning message to confirm that a setup without SMTP notification is intended.


Figure 3-85 shows the window where you specify a contact for heath monitor notification.

Figure 3-85 DB2 Setup wizard: Health monitor notification contact window


16.Complete the health monitor contact information if you want to notify an administrator when a health indicator threshold is breached. If you do not want to specify a contact, choose Defer this task until after installation is complete, and then click Next. The Start copying files window appears (Figure 3-86).

Figure 3-86 DB2 Setup wizard: Current settings and copying files


17.You can scroll through the window to review the current settings for the installation. When you are ready to proceed, click Finish. The DB2 installer will begin the product installation. When DB2 has been successfully installed, an installation summary window appears (Figure 3-87).

Figure 3-87 DB2 Setup wizard: Post-install steps

18.Review the information in the Post-install steps tab to see if there are any additional tasks that you need to complete. You can also check the installation status by clicking the Status report tab (Figure 3-88 on page 169).


Figure 3-88 DB2 Setup wizard: Status report

19.Each of the items displayed in the status report need to indicate Success. Click Finish to exit the DB2 Setup wizard.

3.4.2 Verifying the DB2 installationTo verify that DB2 was successfully installed on a Linux system, first change to the instance owner user ID by using the su command. For example, if your instance owner user ID is db2inst2, type the following command at the host command prompt:

su - db2inst2

This command logs you on to the system as the instance owner. Then, type the following commands:

db2levelexit


The output of the db2level command appears (Example 3-1).

Example 3-1 Output from db2level command

DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL09013"with level identifier "01040107".Informational tokens are "DB2 v9.1.0.3", "s070719", "MI00202", and Fix Pack"3".Product is installed at "/opt/ibm/db2/V9.1".

3.4.3 Installing the DB2 Fix PackTotalStorage Productivity Center V3.3 requires you to install IBM DB2 UDB V8 with Fix Pack 14 or higher. In our installation, we used DB2 V9.1 and, at the time of the writing of this book, Fix Pack 5 was the latest Fix Pack available; therefore, we used Fix Pack 5 during our testing. We used the following procedure to install this Fix Pack. Always first consult the readme file for specific installation instructions for the Fix Pack version that you are installing.

Obtaining and installing the latest DB2 Fix PackComplete the following steps to download and install the latest DB2 Fix Pack:

1. If you have not already done so, log in to your DB2 server as the root user.

2. Create a temporary directory to contain the Fix Pack image and the compressed image files. This directory must have approximately 2 GB of free space. Also, the directory path must not contain any spaces. For example, to create a directory in /tmp called db2fix15, type the following command:

mkdir /tmp/db2fix15

3. Download the latest IBM DB2 UDB Fix Pack from the IBM support FTP site. We downloaded Fix Pack 5 from the following address:

ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2linuxIA32v9/fixpack/FP5_MI00233/v9fp5_linux_universal_fixpack.tar.gz

4. Now, change to the directory to which you downloaded the Fix Pack image:

cd /tmp/db2fix15

5. Decompress the file by using the following command:

gunzip -d v9fp5_linux_universal_fixpack.tar.gz

6. Extract the compressed image files by using this command:

tar -xvf FP15_MI00189.tar


ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2linuxIA32v9/fixpack/FP5_MI00233/v9fp5_linux_universal_fixpack.tar.gz

7. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command:

su - db2inst1

8. Source the environment by issuing the following command:

. ~/sqllib/db2profile

9. Type the following commands to shut down the DB2 environment:

db2 force applications alldb2 terminatedb2stopdb2licd -endexit

10.Switch to the DAS user authority. For example, if your DB2 DAS user is dasusr1, type the following command:

su - dasusr1

11.Type the following commands to source the environment and shut down DB2 DAS:

. ~/das/dasprofiledb2admin stopexit

12.As the root user, issue the following commands to disable the DB2 fault monitor:

cd /opt/ibm/db2/V9.1/bin

./db2fmcu -d

./db2fm -i dasusr1 -D

where dasusr1 is the user ID of your DB2 Database Administration Server (DAS)

13.Change to the directory where you uncompressed this Fix Pack; for example, in our environment, it is /tmp/db2fix15:

cd /tmp/db2fix15

14.Install the Fix Pack by issuing the following command:

./installFixPak -b /opt/ibm/db2/V9.1/

Note: The location that is listed in this command is the default location for a DB2 installation on the Linux operating system. However, if you decide to install DB2 at another location, you must change to that directory structure instead.


15.After the Fix Pack has been successfully installed, you must bind the database instance to the updated code by issuing the db2iupdt command. For example, if your instance name is db2inst2, and you installed DB2 in the default location, type the following commands:

/opt/IBM/db2/V8.1/instance/db2iupdt db2inst2

16.Next you must update the DB2 DAS. For example, if your DB2 DAS user ID is db2tpc, type the following command:

/opt/IBM/db2/V8.1/instance/dasupdt db2tpc

17.Next, you must update the DB2 instance owner’s user profile to update the number of shared memory segments allowed for a process. Edit the userprofile located in the sqllib directory under the instance owner’s home directory. For example, if your instance is db2inst2, type the following command to change to that directory:

cd /home/db2inst2/sqllib

18.Then, edit the userprofile contained in that directory. Add the following lines to the file, and then save the file:

EXTSHM=ONexport EXTSHMdb2set DB2ENVLIST=EXTSHM

19.Next, you must restart DB2. To restart DB2, switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command:

su - db2inst2

20.Source the environment by issuing the following command:

. ~/sqllib/db2profile

21.Type the following commands to start the instance and exit from the instance authority:

db2startexit

22.Finally, you must log in as the DAS user and restart DB2 DAS. Switch to the DAS user authority. For example, if your DB2 DAS user is dasusr1, type the following command:

su - dasusr1

23.Type the following commands to source the environment and start DB2 DAS:

. ~/das/dasprofiledb2admin startexit


3.4.4 Installation of the Agent Manager

Source the db2profile script of your DB2 instance to adapt your environment to be able to execute DB2 tasks. For example, if the DB2 that you want to use for TotalStorage Productivity Center is owned by the user db2inst1, you issue:

. /home/db2inst1/sqllib/db2profile.

To install the Agent Manager, make sure that you have the capability to work with graphical installers. Prepare the GUI according to our instructions:

1. Go to your Agent Manager installation resource and start the installation by issuing the following command:

./setupLinux.bin

Note: Please note that there is a space between . and /home


2. The Agent Manager Installer opens. The first selection that you have to make is whether you will install the Agent Manager in combination with an already existing installation of the WebSphere Application Server or if you want to use the embedded WebSphere Application Server, which is delivered with the Agent Manager installer (Figure 3-89). We do not have a WebSphere Application Server installed already, so we select The embedded WebSphere Application Server delivered with Agent Manager installer. Click Next to continue the installation.

Figure 3-89 InstallShield Wizard: WebSphere Application Server selection

3. The next window prompts you for the installation directory name of the Tivoli Agent Manager (Figure 3-90 on page 175). Choose a location that has sufficient available space. We made sure that /opt has enough available space left. We entered /opt/IBM/AgentManager for the directory name. Click Next to continue.


Figure 3-90 InstallShield Wizard: Directory Name

4. The next window prompts you for the type and location of the database that is used for the Tivoli Agent Manager registry. You can choose among the following six options:

– DB2 database on this computer, which is the default

– DB2 database on another computer (without DB2 Administration Client)

– Local alias to DB2 database on another computer (using DB2 Administration Client)

– Oracle database on this computer

– Oracle database on another computer (using Oracle Database Client)

– Derby database on this computer

We choose DB2 database on this computer, which is the default and suitable for our local installation of DB2.


Make your decision, and click Next to continue the installation (Figure 3-91).

Figure 3-91 InstallShield Wizard: Type and Location of the Database for the Registry


5. Based on the selection that we made on Figure 3-91 on page 176, we are now asked to provide additional information about the DB2 UDB connection (Figure 3-92). Specify the Home Directory of the DB2 instance. In our case, the home directory of the DB2 instance is /home/db2inst1/sqllib. Also, choose a Database Name. In our case, it is IBMCDB, which is also the default. Click Next to continue the installation.

Figure 3-92 InstallShield Wizard: Connection information


6. Enter the database user information in the next window, which is shown in Figure 3-93. Specify a Database Runtime User ID so that you can access the database, and specify a password for that user ID. You also can specify separate user IDs for runtime and installation purposes. You can specify a user ID without the create object authority privilege to be used as the Database Runtime User ID, and you can specify another user ID with full administration privileges as the Database Administrator User ID. Setting it up this way allows you to limit the authority that you give to the Database Runtime User ID. Click Next to continue.

Figure 3-93 InstallShield Wizard: Setting up the user IDs for database access

7. Specify the WebSphere Application Server Connection Information during this step of the installation (Figure 3-94 on page 179). Provide a fully qualified Host Name or Alias of Agent Manager that can be resolved throughout your environment. It is considered a best practice to specify a fully qualified host name that can be resolved through your Domain Name System (DNS). This is the network name that Common agents and resource managers use to connect to the Agent Manager. Working with the hosts file of your machines can leave you with a hard to manage setup for long-term installations. Check whether the specified Agent Manager Registration Port, the Secure Port, and


the Public Port and the Alternate Port for the Agent Recovery Service are suitable for your environment.

You can also specify whether to use port 80 for the Agent Recovery Service. If you do not want to run the Agent Manager as a root user, check this box to not use port 80. Using port 80 for the Agent Recovery Service can be a good practice in environments with a strong firewall in order to enable agent communication with the Agent Manager. Of course, using port 80 for the Agent Recovery Service will conflict with any other service that uses port 80, such as an HTTP server. If you want to run an HTTP server on port 80 on the same machine, you have to change the port for the Agent Recovery Service. If you intend to use the TotalStorage Productivity Center feature to access the GUI through a Web server, consider changing the port for the Agent Recovery Service. But, you can also change the port of the HTTP server, which you then can still use to access the TotalStorage Productivity Center GUI. Click Next to continue.

Figure 3-94 InstallShield Wizard: WebSphere Application Server connection information


8. The next WebSphere Application Server Connection Information window (Figure 3-95) lets you specify the Application Server Name and the Context Root of the Application Server. You also can decide whether to automatically start the Agent Manager each time that the system restarts. Click Next to continue.

Figure 3-95 Install Shield: Application Server Name


9. In the Security Certificates window (Figure 3-96), choose whether you want to use the demonstration certificates or create your own certificates for this installation. We not only consider creating your own certificates to be the best practice, but we also strongly recommend that you create your own certificates for this installation, even if you only plan to use this installation for testing or demonstration purposes. The demonstration certificates only provide you with a low level of security, and they also make long-term installations hard to manage. Click Next to continue.

Figure 3-96 InstallShield Wizard: Security Certificates


10.In the Define the Certificate Authority window, you define the certificate authority by specifying a Certificate Authority Name (the default name is TivoliAgentManagerCA) and a Security Domain (for example, the DomainName), as shown in Figure 3-97. Also, specify a Certificate Authority Password if your security policies require you to examine the contents of the certificate authority truststore, which is considered a best practice. Remember to record this password. Click Next to continue.

Figure 3-97 InstallShield Wizard: Certificate Authority Name


11.Finally, in the Set Passwords window (Figure 3-98), specify an Agent Manager Password and an Agent Registration Password. The Agent Manager Password, which is internally used by the Agent Manager, locks the Agent Manager truststore file and keystore file. The Agent Registration Password is used by Common agents to register with the Agent Manager. Click Next to continue.

Figure 3-98 InstallShield Wizard: Set Passwords


12.You then will be presented with a user input summary that contains an overview of all of your installation parameters and input (Figure 3-99). Verify that everything is correct for your installation. Click Next to start the installation.

Figure 3-99 InstallShield Wizard: User Input Summary


13.First, based on our selections, the embedded version of the WebSphere Application Server is installed and configured (Figure 3-100). The InstallShield Wizard will provide progress updates.

Figure 3-100 InstallShield Wizard: Installation progress


14.After successfully installing the embedded WebSphere Application Server, the Agent Manager installation will provide you with summary information (Figure 3-101). Check the settings and click Next to continue.

Figure 3-101 InstallShield Wizard: Summary information


15.When the Agent Manager installation is almost complete, you have the option to start the AgentManager immediately or defer this task until later (Figure 3-102). We recommend that you choose Yes, start AgentManager now and click Next to continue.

Figure 3-102 InstallShield Wizard


16.The Agent Manager Application Server will be started immediately, as shown in Figure 3-103.

Figure 3-103 InstallShield Wizard progress


17.You will be presented with a summary of your installation and configuration results (Figure 3-104). Check whether every step completed with the status of Successful. Click Next to continue.

Figure 3-104 InstallShield Wizard: Installation status


18.Finally, the installation will prompt you with summary information that the installation of the Agent Manager is complete and that the Agent Manager has been started (Figure 3-105). Click Finish to end the installation of the Agent Manager.

Figure 3-105 InstallShield Wizard: Installation summary

3.4.5 Install TotalStorage Productivity Center V3.3 database schema

After the successful installation of the Agent Manager, continue with the installation of the TotalStorage Productivity Center DB2 database schema.

Add the root user to the DB2 instance groupBefore you continue with the installation, you must add the root user to the group that was created when you created the database instance. If you used the default group ID, the group name is db2grp1. This step is necessary in order to perform the TotalStorage Productivity Center installation.


Follow these steps to add the root user to the instance group, which, in our installation, is named db2grp1:

1. Before you begin, log in to the Linux server as the root user; otherwise, you will not be able to perform this task.

2. Type the following at a command prompt:

groups

This command provides information about which groups contain the root user (Example 3-2).

Example 3-2 groups command output

[root@puget ~]# groupsroot bin daemon sys adm disk wheel man

Make sure that you document which groups contain the root user. If something goes wrong during the addition of the db2grp1 group to the root user’s groups, you need to know which groups contained the root user.

3. To add the root user to db2grp1 group, type this command at a command prompt:

usermod -a -G <groups> <user_id>

where:

<groups> is a list of supplementary groups of which the user is also a member. Each group is separated from the next group by a comma, with no intervening spaces. If the user is currently a member of a group that is not listed, the user will be removed from the group. This behavior can be changed by using the -a option, which appends the user to the current supplementary group list.

<user_id> is a login, which will be added to a group

For Red Hat Linux in this example, the following command adds the root user to the db2grp1 group. Logged on as the root user, execute the following command:

usermod -G root,bin,daemon,sys,adm,disk,wheel,db2grp1 root

Note: Red Hat Linux 4 has at least two ways to add a user to a group. Depending on your preferences, you can use the system-config-users command, which invokes the graphical tool, or you can run the usermod command, which adds the existing user to an existing group.


4. To check if the root user was added to the db2grp1 group, type the following command at a command prompt:

grep db2grp1 /etc/group

This command will provide the content of the record db2grp1 from the group file (Example 3-3).

Example 3-3 Output from grep command

[root@puget ~]# grep db2grp1 /etc/groupdb2grp1:x:102:root

Now, your system is ready for you to install the TotalStorage Productivity Center components.

Install the database schemaIf you are installing TotalStorage Productivity Center V3.3 using electronic images, there are three installation images. If you extract the files from disk1 and disk2 into a directory of the same name, disk1 and disk2, the TotalStorage Productivity Center V3.3 installation program will be able to find the disk2 files. The InstallShield Wizard expects to find disk2 in the same directory as disk1. Having disk2 in another directory causes the installation program to send you an error message. If you use the directory name disk1, you must have disk2 in the same directory as disk1.

Do these steps:

1. First, we install the TotalStorage Productivity Center DB2 database schema. Start the installation of TotalStorage Productivity Center by executing:

./setup.sh

The graphical installer prompts you with a selection window to choose the installer’s language, as shown in Figure 3-106. Choose English and click OK to continue. The initialization of the installation wizard window appears and takes a few minutes.

Figure 3-106 Language selection window


2. The TotalStorage Productivity Center installation program prompts you with the International Program License Agreement window, as shown in Figure 3-107. Read through the program license agreement. To continue, accept the license agreement by selecting I accept the terms of the license agreement and click Next.

Figure 3-107 TotalStorage Productivity Center Installer: License agreement


3. The next window (Figure 3-108) prompts you for the type of installation that you want to perform. Choose Custom installation to be able to perform the four-tier installation approach that we take. Choose an installation location for TotalStorage Productivity Center that has sufficient available space. We use the default, which is /opt/IBM/TPC. Click Next to continue.

Figure 3-108 TotalStorage Productivity Center Installer: Custom installation


4. The custom installation window lets you choose the components that you want to install (Figure 3-109). Choose only Create database schema and remove the check marks in all of the other check boxes, so that you only create the database schema and nothing else. Click Next to continue.

Figure 3-109 TotalStorage Productivity Center Installer: Create database schema


5. The next window (Figure 3-110) allows you to enter the database administrator information that is used to connect to the database during installation and uninstallation. In our environment, the database administrator username is db2inst2. Click Next to continue.

Figure 3-110 TotalStorage Productivity Center Installer: Database administrator


6. The next window allows you to specify the new database schema information (Figure 3-111). Enter the information that the product will use when communicating with the DB2 instance and creating the required repository tables. Be careful not to choose a local database that already exists. IBMCDB is the Common agent database, and TOOLSDB is the DB2 tools database. Both databases must not be used for TotalStorage Productivity Center installation. Choose Create local database and enter a name for the database. The default name for the newly created TotalStorage Productivity Center database is TPCDB. The schema creation details allow you to further specify the size and layout of the TPCDB. If you are not a DB2 specialist, accept the defaults. Click Next to continue. If you click Schema creation details, the Figure 3-112 on page 198 appears.

Figure 3-111 TotalStorage Productivity Center Installer: Database schema information

7. The window shown in Figure 3-112 on page 198 allows you to change the default space assigned to the database. Review the defaults and make any changes. In our installation, we accepted the default values.

For better performance, we recommend that you:

– Allocate TEMP DB on another physical disk than the TotalStorage Productivity Center components.

– Create larger Key and Big Databases.


Select System managed (SMS), click OK, and click Next to proceed.

Figure 3-112 TotalStorage Productivity Center Installer: Database schema creation


8. The installer will present a window with summary information (Figure 3-113). Check the information carefully to ensure that it represents exactly what you want. If everything is correct, click Install to continue.

Figure 3-113 TotalStorage Productivity Center Installer: Database schema summary


9. The database schema installation begins. The TotalStorage Productivity Center installer provides you with progress updates, as shown in Figure 3-114.

Figure 3-114 TotalStorage Productivity Center Installer: Installation progress

10.After the installation is finished, you are presented with an installation summary window, as shown in Figure 3-115 on page 201. Make sure that the installation was successful, and click Finish to end the installation.


Figure 3-115 TotalStorage Productivity Center Installer: Installation summary

3.4.6 Install TPC V3.3 Data server, Device server, CLI, and GUIFollow these steps to install the TotalStorage Productivity Center V3.3, the Data server, the Device server, the CLI, and the GUI:

1. To continue with the TotalStorage Productivity Center installation, start the installer again by executing this command:

./setup.sh

The graphical installer prompts you with a selection window to choose the language to use for this installation (Figure 3-116). Choose English and click OK to continue.

Figure 3-116 TotalStorage Productivity Center Installer: Language selection


2. The initialization of the installation wizard takes a short period of time. During this time, you see the information window shown in Figure 3-117.

Figure 3-117 TotalStorage Productivity Center Installer: Initialization of installer

3. The TotalStorage Productivity Center installation GUI opens and prompts you with the program license agreement. Read through the International Program License Agreement (Figure 3-118). To continue, select I accept the terms of this license agreement and click Next.

Figure 3-118 Installer: License agreement


4. The next window prompts you for the type of installation that you want to perform (Figure 3-119). Choose Custom installation to be able to continue the two-tier installation approach that we take. The installation location for TotalStorage Productivity Center will be detected automatically. We use the default location, which is /opt/IBM/TPC. Click Next to continue.

Figure 3-119 Installer: Type of installation


5. The window shown in Figure 3-120 lets you choose the components that you want to install in this run. Note that the Create database schema check box will be grayed out, because we have already installed the database schema. Now, select the check boxes for Data Server, Device Server, GUI, CLI, Data Agent, and Fabric Agent so that you install all of these components. Click Next to continue.

Figure 3-120 Installer: Component installation


6. Enter the database administrator name and password information to be used during the installation in the window shown in Figure 3-121, and click Next to continue.

Figure 3-121 Installer: Database administrator information


7. Because we have already installed the DB2 database schema, you now have to select that DB2 database schema from the list of available databases under the Use local database selection list box, as shown in Figure 3-122. Select the TPCDB database. Click Next to continue.

Figure 3-122 Installer: Database schema information

8. The next window, which is shown in Figure 3-123 on page 207, lets you specify the Data server, Device server, and Data agent information:

– Enter a fully qualified host name for the Data server and the Device server. This host name needs to be resolvable by your DNS from all of the machines that you plan to use in combination with TotalStorage Productivity Center.

– Specify a Data server port and a Device server port.

– Specify the TPC superuser.

– Specify a Host authentication password for the Fabric agents to communicate with the Device server, that is, the host communication password.

– You will not be able to specify a Data server account password, which is for Windows installations only.

– Specify a WebSphere Application Server admin ID and a password. Click Security roles to go to the window shown in Figure 3-123 on page 207.


Click NAS discovery to go to the window shown in Figure 3-125 on page 209. Click Data agent options to go to the window shown in Figure 3-126 on page 210.

– Click Next to continue with the installation.

Figure 3-123 Installer: Data server, Device server, and Agent information


9. You can create Advanced Security Roles Mapping, as shown in Figure 3-124. Leave the default values and click OK to get back to Figure 3-123 on page 207.

Figure 3-124 Installer: Advanced Security Roles Mapping


10.The NAS Discovery Information (Figure 3-125) is optional. Leave it as it is and click OK to go back to the previous window. The NAS Discovery Information can be entered at a later point in time.

Figure 3-125 Installer: NAS Discovery Information


11.Configure the default options for Data agents in the window shown in Figure 3-126. Enable the check box to have an agent run a scan when first installed. Enable the check box to allow an agent to run a script sent by the server. These functions are recommended best practices. Click OK to continue.

Figure 3-126 Installer: Data agent options



12.Specify the Agent Manager information in Figure 3-127. Enter a fully qualified host name, the Agent Manager secured port, and the Agent Manager public port. Specify the Data server and Device server registration information and the Common agent registration password. Click Next to continue.

Figure 3-127 Installer: Agent Manager information


13.The next window (Figure 3-128) prompts you for the Common agent information selection. Click Install the new common agent at the location listed below. The default location is /opt/IBM/TPC/ca with an agent port of 9510. Click Next to continue.

Figure 3-128 Installer: Common agent selection


14.The next window, which is shown in Figure 3-129, presents you with the installation summary information. Verify that everything is correct and click Install to begin the actual installation.

Figure 3-129 Installer: Installation information


15.After the installation completes, you are presented with a summary window, as shown in Figure 3-130. Click Finish to complete the installation.

Figure 3-130 Installer: Installation status

You can now start the TotalStorage Productivity Center GUI by issuing the following command:

/usr/local/bin/TPC

Note: If you are logging in to the IBM TotalStorage Productivity Center GUI for the first time after installing the product and did not set up a IBM TotalStorage Productivity Center user role, you might not be able to log in. It is enough to create a user ID that is a member of the 'adm' group.


3.5 AIX installation

This section describes the installation of TotalStorage Productivity Center in an AIX environment. In our environment, we used AIX V6.1 64-bit and DB2 V9.1 64-bit as well.

3.5.1 DB2 installation After you have verified that your system has met the minimum system requirements for installing TotalStorage Productivity Center, including adequate free disk space, the first component for you to install is IBM DB2 UDB Enterprise Server Edition V9.1. After it is successfully installed, you will then install the DB2 Fix Pack. At a minimum, Fix Pack 4 is required for AIX V6.1 and Fix Pack 2 for AIX 5L V5.x.

Follow these steps to perform the installation of IBM DB2 UDB.

Accessing the installation media using the CDIf you are accessing the installation media using a downloaded image, skip to the next section.

To access the installation media using the CD:

1. If you have not already logged on, log on to the system as the root user.

2. Insert the CD into the CD-ROM or DVD-ROM drive on your system.

3. Create a mount point for the media. For example, if you want to mount the CD at /cdrom, type the following command:

mkdir /cdrom

4. Next, mount the disc in read-only mode at the mount point that you created in the previous step. For example:

mount -o ro /dev/cd0 /cdrom

5. Change to the newly mounted disc. For example:

cd /cdrom

6. Proceed to “Preparing the display” on page 216.

Accessing the installation media using a downloaded imageTo access the installation media using a downloaded image:

1. If you have not already logged on, log on to the system as the root user.


2. Create a temporary directory to contain the installation image and the compressed image files. This directory must have approximately 2 GB of free space. Also, the directory must not contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command:

mkdir /usr/tarfiles

3. Download or copy the installation image to the temporary directory that you created.

4. Change to the directory where you have stored the image, for example:

cd /usr/tarfiles

5. Extract the image files by following the instructions supplied at the repository from which you downloaded the image, which might involve running the tar or gunzip commands, or a combination of both commands. For example:

tar -xvf db2.tar

6. Change to the installation directory, which you extracted from the image. For example:

cd ese.sbcsaix1

Preparing the displayThis version of the DB2 installer uses a graphical, Java-based interface. If you are installing DB2 using a local graphical display, proceed to “Beginning the installation”. However, if you are installing from a remote terminal session, you must set up an X Window System display or a Virtual Networking Computing (VNC) Viewer connection prior to beginning the installation process.

If you decide to use X Window System server, first you must start your local X Window System server application. Examples are Hummingbird Exceed or Cygwin.

If you decide to use VNC Viewer, first you have to start the VNC Server on an AIX server, set up a connection password, and then, start the local VNC Viewer.

Beginning the installationFollow these steps to perform the installation of IBM DB2 UDB:

1. At the command prompt on the host, type the following command:

./db2setup


The DB2 setup launchpad opens (Figure 3-131).

Figure 3-131 DB2 Setup launchpad


2. Click Install products to begin the installation. A new Setup window appears (Figure 3-132), which asks which products you want to install.

Figure 3-132 DB2 product selection


3. Select the option DB2 UDB Enterprise Server Edition and click Install New. The Welcome to the DB2 Setup wizard now appears (Figure 3-133).

Figure 3-133 Welcome to the DB2 Setup wizard


4. Click Next. The Software License Agreement window appears (Figure 3-134).

Figure 3-134 DB2 Software License Agreement


5. You must click Accept and then click Next to proceed. The Select the Installation Type window appears (Figure 3-135).

Figure 3-135 DB2 installation type


6. Select Typical and then click Next. The Select the installation action window appears (Figure 3-136).

Figure 3-136 DB2 installation action


7. Select Install DB2 UDB Enterprise Server Edition on this computer and save my settings in a response file and click Next. The Select the installation directory window appears (Figure 3-137).

Figure 3-137 DB2 Select installation directory


8. Select the installation directory according to your environment; /opt/IBM/db2/V9.1 is the default. Click Next to continue. The Set user information for the DB2 Administration user window appears (Figure 3-138).

Figure 3-138 DB2 Administration Server user information


9. If you want the installer to create a DB2 Administration Server (DAS) user ID, you must enter a unique user name for the DAS user in the User name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank, and you check Use default UID and Use default GID, the system will assign a UID and GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the DAS user. After you have completed this panel, click Next. The Set up a DB2 instance window appears (Figure 3-139).

Figure 3-139 Set up a DB2 instance


10.Select Create a DB2 instance and click Next. The Select how the instance will be used (instance partitioning) window appears (Figure 3-140).

Figure 3-140 DB2 instance partitioning


11.Select Single-partition instance and click Next. The Set user information for the DB2 instance owner window appears (Figure 3-141).

Figure 3-141 Set user information for the DB2 instance owner


12.If you want the installer to create a DB2 instance owner user ID, you must enter a unique user name for the instance owner in the User name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank, and you check Use default UID and Use default GID, the system will assign a UID and GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the instance owner. After you have completed this window, click Next. The Set user information for the Fenced user window appears (Figure 3-142).

Figure 3-142 Set user information for the fenced user


13.If you want the installer to create a DB2 fenced user ID, you must enter a unique user name for the fenced user in the User name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank, and you check Use default UID and Use default GID, the system will assign a UID and GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the fenced user. After you have completed this window, click Next. The Prepare the DB2 tools catalog window appears (Figure 3-143).

Figure 3-143 Prepare the DB2 tools catalog


14.Click Do not prepare the DB2 tools catalog and then click Next. The Set up notifications window appears (Figure 3-144).

Figure 3-144 Set up notifications


15.Choose the options on this window that pertain to your specific environment. If you already have DB2 servers in your environment, it might benefit you to use a contact list on an existing DB2 server. Select Remote and enter the name of the remote DB2 server from which to obtain the contact list. Otherwise, choose the default options of Local and Enable notification. The local host name is displayed in the Notification SMTP server field by default. You can change this option to suit your environment. After you have filled out this panel, click Next. The Specify a contact for health monitor notification window appears (Figure 3-145).

Figure 3-145 Specify a contact for the DB2 health monitor


16.Complete this window based on your particular environment. If you do not want to specify a contact, choose Defer this task until after installation is complete and then click Next. The Start copying files and create response file window appears (Figure 3-146).

Figure 3-146 DB2 start copying files

17.You can scroll through the window to review the installation summary. When you are ready to proceed, click Finish. The DB2 Setup wizard begins the product installation and performs the required configuration. A progress window appears (Figure 3-147 on page 233).


Figure 3-147 DB2 installation progress

18.When DB2 has been successfully installed, an installation summary window appears (Figure 3-148).

Figure 3-148 DB2 post-installation steps


19.You can review the information in the Post-install steps tab to see if there are any additional tasks that you need to complete. You can also click the Status report tab (Figure 3-149).

Figure 3-149 DB2 installation status report

20.Each of the items in the status report needs to indicate Success. Click Finish to close the installer.

3.5.2 Verifying the DB2 installationTo verify that DB2 was successfully installed, first change to the instance owner user ID by using the su command. For example, if your instance owner user ID is db2inst1, type the following command at the host command prompt:

su - db2inst1

This command will log you on to the system as the instance owner. Then, type the following commands:

db2levelexit


The output of the db2level command appears (Example 3-4).

Example 3-4 Output of the db2level command

DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09010"with level identifier "02010107".Informational tokens are "DB2 v9.1.0.0", "s060629", "AIX64", and Fix Pack "0".Product is installed at "/opt/IBM/db2/V9.1".

Removing the CD from the serverIf you accessed the installation media using a CD, now unmount the CD and remove it from the system by completing the following steps:

1. Type the following command at a host command prompt:

umount /cdrom

2. Remove the CD from the drive by pressing the button on the front panel of the CD-ROM or DVD-ROM drive, which will eject the media tray.

3. Remove the CD from the media tray, and close the media tray by pressing the button again.

3.5.3 Installing the DB2 Fix PackTotalStorage Productivity Center requires you to install IBM DB2 UDB with Fix Pack 4 or higher. At the time of writing this book, Fix Pack 5 was the latest Fix Pack available. We used Fix Pack 5 during our testing. We used the following procedure to install Fix Pack 5. Always consult the readme file for specific installation instructions for the Fix Pack version that you are installing.

Obtaining and installing the latest DB2 Fix PackComplete the following steps to download and install the latest DB2 Fix Pack:

1. If you have not already logged in, log in to your DB2 server as the root user.

2. Create a temporary directory to contain the Fix Pack image and the compressed image files. This directory must have approximately 2 GB of free space. Also, the directory must not contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command:

mkdir /usr/tarfiles


3. Download the latest IBM DB2 UDB Fix Pack from the IBM support FTP site. We downloaded Fix Pack 5 from the following address:

ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2aix5v9/fixpack/FP5_U815922/v9fp5_aix_universal_fixpack.tar.gz

4. Change to the directory where you stored the Fix Pack image. For example, if you downloaded the file to /usr/tarfiles, type the following command:

cd /usr/tarfiles

5. Extract the compressed image files. For Version 10 of the Fix Pack, the command is:

gunzip -c FP14_U810098.tar.Z | tar -xvf -

6. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command:

su - db2inst1

7. Source the environment by issuing the following command:

. $HOME/sqllib/db2profile

8. Type the following commands to shut down the DB2 environment:

db2 force applications alldb2 terminatedb2stopdb2licd -end$HOME/sqllib/bin/ipcleanexit

9. Switch to the DAS user authority. For example, if your DB2 DAS user is db2tpc, type the following command:

su - dasusr1

10.Type the following commands to source the environment and shut down DB2 DAS:

. $HOME/das/dasprofiledb2admin stopexit

11.As the root user, issue the following commands to unload shared libraries and disable the DB2 fault monitor:

/usr/sbin/slibcleancd /opt/IBM/db2/V9.1/bin


ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2aix5v9/fixpack/FP5_U815922/v9fp5_aix_universal_fixpack.tar.gz

./db2fmcu -d

./db2fm -i dasusr1 -D

where dasusr1 is the user ID of your DAS user. In our environment, we use db2tpc.

12.Change to the directory that was created automatically when the Fix Pack files were uncompressed. For Version 10 of the Fix Pack, the directory is named fixpak.s061108. Type the following command:

cd fixpak.s061108

13.Install the Fix Pack by issuing the following command:

./installFixPak -b /opt/IBM/db2/V9.1/

14.After the Fix Pack has been successfully installed, you must bind the database instance to the updated code by issuing the db2iupdt command. For example, if your instance name is db2inst1, and you installed DB2 in the default location, type the following commands:

/opt/IBM/db2/V9.1/instance/db2iupdt db2inst1

15.Next, you must update the DB2 DAS. For example, if your DB2 DAS user ID is dasusr1, type the following command:

/opt/IBM/db2/V9.1/instance/dasupdt dasusr1

16.Next, you must update the db2 instance owner’s user profile to update the number of shared memory segments allowed for a process. Edit the userprofile that is located in the sqllib directory under the instance owner’s home directory. For example, if your instance is db2inst1, type the following command to change to that directory:

cd /home/db2inst1/sqllib

17.Then, edit the userprofile contained in that directory. Add the following lines to the file and then save the file:

EXTSHM=ONexport EXTSHMdb2set DB2ENVLIST=EXTSHM

18.Next, you must restart DB2. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command:

su - db2inst1

Note: The location that is listed is the default location for the DB2 installation. However, if you selected to install DB2 at another location, change to that directory structure instead.


19.Source the environment by issuing the following command:

. $HOME/sqllib/db2profile

20.Type the following commands to start the instance and exit from the instance authority:

db2startexit

21.Finally, you must log in as the DAS user and restart DB2 DAS by switching to the DAS user authority. For example, if your DB2 DAS user is dasusr1, type the following command:

su - dasusr1

22.Type the following commands to source the environment and start DB2 DAS:

. $HOME/das/dasprofiledb2admin startexit

Add the root user to the DB2 instance groupYou must add the root user to the group that you created when you created the database instance. If you used the default group user ID, the group name is db2grp1. This step is necessary in order to perform the TotalStorage Productivity Center installation.

Follow these steps to add the root user to the instance group:

1. Type the following command at a command prompt:

smit group

The SMIT interface appears and shows the Groups menu.

2. Select the option Change / Show Characteristics of a Group.

3. In the Group NAME field, enter the name of the group to be modified. If you used the default group ID, enter the name db2grp1 and press Enter.

4. Highlight the USER list field and press F4. The USER list menu appears.

5. Highlight the root user ID and press F7 to select it.

6. Highlight the DB2 instance owner user ID and press F7 to select it. For example, select the user ID db2inst1, then press Enter. The Change Group Attributes screen reappears. Ensure that both the root user and the DB2 instance owner user ID appear in the USER list field, and then press Enter.

7. When the OK status appears, press F10 to exit SMIT (press F12 if using the graphical version).


3.5.4 Agent Manager installation for AIXAfter you have completed the installation of IBM DB2 UDB and applied the latest Fix Pack, then you can install Agent Manager. For small and medium-sized deployments, install Agent Manager on the same server as DB2. For Enterprise deployments, you can install Agent Manager on a separate server if you want. The only change to the install procedure is connecting to a remote DB2 server instead of a local DB2 server.

By default, the Agent Manager installer will also install IBM WebSphere Application Server - Express V6.0.2 (WebSphere Express).

Follow these steps to perform the installation of Agent Manager.

Accessing the installation media using a CDIf you are accessing the installation media using a downloaded image, skip to “Accessing the installation media using a downloaded image” on page 239.

To access the installation media using a CD:

1. If you have not already logged in, log on to the system as the root user.


3. If you have not already created a mount point for the media, create a mount point for the media now. For example, if you want to mount the disc at /cdrom, type the following command:

mkdir /cdrom

4. Next, mount the disc in read-only mode at the mount point that you created in the previous step, for example:


5. Change to the newly mounted filesystem, for example:

cd /cdrom

6. Proceed to “Preparing the display” on page 240.

Accessing the installation media using a downloaded imageTo access the installation media using a downloaded image:

1. If you have not already logged in, log on to the system as the root user.


2. Create a temporary directory to contain the installation image and the compressed image files. This directory must be created on a filesystem, which has approximately 2 GB of free space. Also, the directory must not contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command:

mkdir /usr/tarfiles

3. Download or copy the installation image to the temporary directory that you have created.


cd /usr/tarfiles

5. Extract the image files by following the instructions supplied at the repository from which you downloaded the image. This step might involve running the tar or gunzip commands, or a combination of both commands, for example:

tar -xvf agentmanager.tar

6. Change to the installation directory that was created automatically, which you extracted from the image, for example:

cd EmbeddedInstaller

Preparing the displayThis version of the Agent Manager installer uses a graphical, Java-based interface. If you are installing using a local graphical display, proceed to “Beginning the installation”. However, if you are installing from a remote terminal session, you must set up an X Window System display prior to beginning the installation process.

First, you must start your local X Window System server application, such as Hummingbird Exceed or Cygwin.

Beginning the installationFollow these steps to perform the installation of Agent Manager:

1. At the command prompt on the host, type the following command:

./setupAix.bin

The Agent Manager Installer opens. You first select whether you will install the Agent Manager in combination with an already existing installation of the WebSphere Application Server or if you want to use the embedded WebSphere Application Server, which is delivered with the Agent Manager installer (Figure 3-150 on page 241).


We do not have a WebSphere Application Server installed already, so we select The embedded version of the WebSphere Application Server delivered with the Agent Manager installer. Click Next to continue the installation.

Figure 3-150 InstallShield Wizard: WebSphere Application Server selection


2. The next window (Figure 3-151) prompts you for the installation directory of the TotalStorage Agent Manager. Choose a location that has sufficient space. We made sure that the /opt has enough available space and used the default installation directory, which is /opt/IBM/AgentManager. Click Next to continue.

Figure 3-151 InstallShield Wizard: Agent Manager installation directory name

3. The next window in Figure 3-152 on page 243 prompts you for the type and location of the database used for the TotalStorage Agent Manager registry. You can choose between the following six options:

– DB2 database on this computer. This is the default.

– DB2 database on another computer (without DB2 Administration Client).

– Local alias to a DB2 database on another computer (using DB2 Administration Client).

– Oracle database on this computer.

– Oracle database on another computer (using Oracle Database Client).

– Derby database on this computer.


We choose DB2 database on another computer (without DB2 Administration Client), which is the default. If you select the first option, DB2 database on this computer, the installation will fail while creating the Agent Manager registry database. Choosing the second option makes the installer use the correct JDBC driver.

Make your selections based on your installation, and click Next to continue the installation.

Figure 3-152 InstallShield Wizard: Database selection for the registry


4. Based on the selection that we have made on the previous window, we are now asked to provide additional information about the DB2 UDB connection (Figure 3-153). Specify the Home Directory of the DB2 instance (in our case, it is /home/db2inst1/sqllib). Also, choose a Database Name (in our case, it is IBMCDB, which is also the default). Click Next to continue the installation.

Figure 3-153 Install Wizard: Database connection information


5. Enter Database User Information in Figure 3-154. Specify a Database Runtime User ID and specify a password for that user ID. You also can specify separate user IDs for runtime and installation purposes. You can specify a user ID with full administration privileges for the Database Administrator User ID, and you can use another user ID without the create object authority capability to be used as the Database Runtime User ID. This design allows you to limit the authority that you give to the Database Runtime User ID. Click Next to continue.

Figure 3-154 InstallShield Wizard: Database User Information


6. In Figure 3-155 on page 247, you specify the WebSphere Application Server Connection Information:

– Provide a fully qualified Host Name or Alias for Agent Manager that can be resolved throughout your environment. The best practice is to specify a fully qualified host name that can be resolved through your DNS. Working with the HOSTS file of your machines can leave you with a hard to manage setup for long-term installations.

– Check whether the specified Agent Manager Registration Port, the Secure Port, and the Public Port and Alternate Port for the Agent Recovery Service are suitable for your environment. You can also decide whether to use port 80 for the Agent Recovery Service. If you do not want to run the Agent Manager as a root user, you must check this box to not use port 80. Using port 80 for the Agent Recovery Service can be a good practice in an environment with a firewall to enable agent communication with the Agent Manager. Of course, using port 80 for the Agent Recovery Service conflicts with any other service that might use port 80, such as an HTTP server. If you want to run an HTTP server on port 80 on the same machine, you must change the port for the Agent Recovery Service.

If you intend to use the TotalStorage Productivity Center feature to access the GUI through a Web server, consider changing the port for the Agent Recovery Service. You can also change the port of the HTTP server, which then can be used to access the TotalStorage Productivity Center GUI.



Figure 3-155 InstallShield Wizard: WebSphere Application Server connection information


7. The window shown in Figure 3-156 lets you specify the Application Server Name and the Context Root of the Application Server. You also can decide whether to automatically start the Agent Manager each time that the system restarts. Click Next to continue.

Figure 3-156 InstallShield: WebSphere Application Server connection information


8. The Security Certificates window (Figure 3-157) lets you choose whether you want to use the demonstration certificates or create your own certificates for this installation. It is not only considered the best practice to create your own certificates, but we also strongly recommend that you create your own certificates for this installation, even if you only plan to use the installation for testing or demonstration purposes. The demonstration certificates only provide a low level of security, and they also make long-term installations hard to manage. Click Next to continue.

Figure 3-157 InstallShield Wizard: Certificates selection


9. Define the certificate authority by specifying a Certificate Authority Name (the default is TotalStorageAgentManagerCA) and a Security Domain (for example, your DomainName), as shown in Figure 3-158. Also, specify a Certificate Authority Password if your security policies require you to examine the contents of the certificate authority truststore, which is a best practice. Click Next to continue.

Figure 3-158 InstallShield Wizard: Define the Certificate Authority


10.Finally, specify an Agent Manager Password and an Agent Registration Password on the Set Passwords window (Figure 3-159). The Agent Manager Password locks the Agent Manager truststore file and the keystore file. It is used internally by the Agent Manager. The Agent Registration password is used by Common agents to register with the Agent Manager. Click Next to continue.

Figure 3-159 InstallShield Wizard: Agent Manager Password


11.The User Input Summary information window in Figure 3-160 contains an overview of all of the decisions that you have just made. Verify that everything is correct. Click Next to start the installation.

Figure 3-160 InstallShield Wizard: User Input Summary


12.After successfully installing the Embedded WebSphere Application Server, the Agent Manager installation provides you with the summary information shown in Figure 3-161. Check the settings and click Next to continue.

Figure 3-161 InstallShield Wizard: AgentManager Application Server location


13.When the Agent Manager installation is almost complete, you are asked whether to start the Agent Manager right now or defer this task until later (Figure 3-162). Choose Yes, start AgentManager now and click Next to continue.

Figure 3-162 InstallShield Wizard: Start AgentManager


14.You are presented with a summary of your installation and configuration results, as shown in Figure 3-163. Verify whether every step completed with the status of Successful. Click Next to continue.

Figure 3-163 InstallShield Wizard: Installation and configuration results summary


15.Finally, the installation provides you with summary information that the installation of the Agent Manager is complete and that the Agent Manager has been started (Figure 3-164). Click Finish to end the installation.

Figure 3-164 InstallShield Wizard: Installation summary

Removing the CD from the serverIf you accessed the installation media using CD, now unmount the CD and remove it from the system by completing the following steps:

1. Type the following at a host command prompt:

umount /cdrom

2. Remove the CD from the drive by pressing the button on the front panel of the CD-ROM or DVD-ROM drive, which ejects the media tray.

3. Remove the CD from the media tray, and close the media tray by pressing the button again.


3.5.5 Install TotalStorage Productivity Center V3.3 database schemaAfter you have completed the installation of DB2 and Agent Manager, then you should continue creating the database schema. In this chapter, we document the Custom installation. We show how you can select each component individually. While we recommend the Custom installation, you also can select all components to be installed in one invocation of the installer, which is called the Typical installation.

Installation order of the componentsAfter installing the prerequisites, it is ideal to install the components in the following order:

� Database schema� Data server� Device server� GUI and CLI� Data agent and Device agent

Accessing the installation media using CDIf you are accessing the installation media using a downloaded image, skip to “Accessing the installation media using a downloaded image” on page 258.

Follow these steps to perform the installation of IBM TotalStorage Productivity Center V3.3:

1. If you have not already logged on, log on to the DB2 system as the root user.


3. If you have not already created a mount point, create a mount point for the media. For example, if you want to mount the disc at /cdrom, type the following command:

mkdir /cdrom

4. Next, mount the disc in read-only mode at the mount point that you created in the previous step, for example:


5. Change to the newly mounted filesystem, for example:

cd /cdrom

Proceed to “Preparing the display” on page 240.


Accessing the installation media using a downloaded imageTo access the installation media by using a downloaded image:

1. If you have not already logged on, log on to the DB2 system as the root user.

2. Create a temporary directory to contain the installation image and the compressed image files. This directory must be created on a filesystem that has approximately 2 GB of free space. Also, the directory must not contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command:

mkdir /usr/tarfiles

3. Download or copy the installation image to the temporary directory that you created.


cd /usr/tarfiles

5. Extract the image files by following the instructions supplied at the repository from which you downloaded the image. This might involve running the tar or gunzip commands, or a combination of both commands, for example:

tar -xvf TPC_3.3.0_aix_disk1.tar

Sourcing the environmentIf you will be installing TotalStorage Productivity Center on the same server on which you installed DB2, you need to source the DB2 environment. For example, if your DB2 instance is named db2inst1, type the following command:

. /home/db2inst1/sqllib/db2profile

Assigning filesystem ownershipIf you created filesystems to contain DB2 tables and temporary space, you must change the owner of those filesystems to the DB2 instance owner so that the appropriate database files can be created. For example, if you created the filesystem /dbfiles to house DB2 tables and created the filesystem /dbtemp to house DB2 temporary storage, and your instance owner is db2inst1, issue the following command on your DB2 server:

chown db2inst1 /dbfiles /dbtemp

Note: You must install TotalStorage Productivity Center as the root user. However, you must still source the environment using the instance owner.


Installing the database schemaWe consider it a best practice to split the installation of TotalStorage Productivity Center into the following parts:

� Install the TotalStorage Productivity Center DB2 database schema.� Install the Data Server and the Device Server, CLI, and GUI.� Optionally, install Data Agent or Fabric Agent.

Follow these steps to perform the installation of the database schema for TotalStorage Productivity Center:

1. At the command prompt on the DB2 host, type the following command:

./setup.sh

2. The TotalStorage Productivity Center Installer opens and prompts you to select an installation language (Figure 3-165). Click OK to continue. The initialization of the installation wizard window appears and takes a few minutes.

Figure 3-165 TotalStorage Productivity Center installation language selection


3. Select the language from the drop-down list that you want to use for the installation, and then click OK. The TotalStorage Productivity Center installer will then initialize. The first item to display is the International Program License Agreement window (Figure 3-166).

Figure 3-166 TotalStorage Productivity Center license agreement


4. Click I accept the terms of the license agreement, and then click Next. The installation types window appears (Figure 3-167).

Figure 3-167 TotalStorage Productivity Center installation types


5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. After you have completed this window, click Next. The “Select one or more components to install on the local or remote computer” window appears (Figure 3-168).

Figure 3-168 TotalStorage Productivity Center component selection


6. Remove the check mark from all of the options except Create database schema. Click Next. The Database administrator information window appears (Figure 3-169).

Figure 3-169 TotalStorage Productivity Center database administrator


7. Enter the user ID for the DB2 instance owner in the Database administrator field, and enter the instance owner’s password in the Password field. Click Next to continue. The New Database schema information window appears (Figure 3-170).

Figure 3-170 TotalStorage Productivity Center database schema information

8. You need to enter the DB2 instance owner’s user ID in the DB user ID field and the instance owner’s password in the Password field. Then, you can choose which database connection type to use for TotalStorage Productivity Center:

– If you are upgrading from a current version of TotalStorage Productivity Center, choose Use local database. Enter the port, database name, full path, and instance name in the appropriate fields.

– If this is a new installation (not an upgrade), choose Create local database. The default database name is TPCDB. We recommend that you do not change this name.

After you have selected the database connection type that suits your requirements, click Schema creation details. The Database schema creation information window appears (Figure 3-171 on page 265).


Figure 3-171 TotalStorage Productivity Center database schema details

9. The default entry in the Schema name field is TPC. We recommend that you do not change this field from the default setting. You then have the option of placing the various tablespaces in various directories or filesystems and of setting an initial database size. For all but the largest Enterprise deployments, database sizes of 200 MB are sufficient for the initial creation.

For the best performance in medium and Enterprise deployments, consider placing the tablespaces on separate filesystems and on separate disk devices. If you have already created these filesystems, enter their paths in the Normal, Key, Big, and Temp fields, or click Browse to search for them. The Normal, Key, and Big databases can be housed in the same filesystem. The Temp database needs to be housed on a separate filesystem for the best performance.

The differences between choosing System managed (SMS) and Database managed (DMS) containers are discussed in 2.3.3 “SMS or DMS tablespace type” on page 45.

If you select Database managed (DMS), you can enter a path where you house log files and an initial size. Log files need to be housed separately from the tablespaces for best performance. For all but the largest Enterprise deployments, an initial size of 20 MB is sufficient.


After you have completed this window, click OK. You are returned to the database schema information window. In that window, click Next. The summary information window appears (Figure 3-172).

Figure 3-172 TotalStorage Productivity Center installation summary


10.Click Install to begin the database schema installation. A progress window appears (Figure 3-173).

Figure 3-173 TotalStorage Productivity Center installation progress


11.When the installation is complete, the installation results window appears (Figure 3-174).

Figure 3-174 TotalStorage Productivity Center installation results

12.Click Finish to exit the installer.

3.5.6 Install TPC V3.3 Data server, Device Server, CLI and GUIAfter you have finished creating the database schema, you are ready to install the Data Server, the Device Server, the CLI, and the GUI. Follow these steps to complete the installation process:

1. At the command prompt on the Data server host, in the installation media directory, type the following command:

./setup.sh

2. The TotalStorage Productivity Center installer opens and prompts you to select an installation language. The prompt appears (Figure 3-175 on page 269).


Figure 3-175 TotalStorage Productivity Center installation language selection

3. Select the language from the drop-down list that you want to use for the installation, and then click OK. The TotalStorage Productivity Center Installer then initializes. The first item to display is the International Program License Agreement window (Figure 3-176).

Figure 3-176 TotalStorage Productivity Center license agreement


4. Click I accept the terms of the license agreement, and then click Next. The installation types window appears (Figure 3-177).

Figure 3-177 TotalStorage Productivity Center installation types


5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. After you have completed this window, click Next. The “Select one or more components to install on the local or remote computer” window appears (Figure 3-178).

Figure 3-178 TotalStorage Productivity Center component selection


6. The window lets you choose the components to install in this run. Note that Create database schema is grayed out, because we have already installed the database schema. Now, select the check boxes for Data Server, Device Server, CLI, and GUI. Also, Register with the agent manager should be selected. Click Next. The Database administrator information window appears (Figure 3-179).

Figure 3-179 TotalStorage Productivity Center database administrator

7. Enter the user ID for the DB2 instance owner in the Database administrator field and the instance owner’s password in the Password field, and then click Next. The New database schema information window appears (Figure 3-180 on page 273).


Figure 3-180 Data server database schema information

8. Enter the DB2 instance owner’s user ID in the DB user ID field and the instance owner’s password in the Password field:

– If you are installing Data server on the same machine where DB2 is installed, check Use local database. The local database information is populated automatically. Highlight the local database to use.

– If you are installing Data server on a separate machine, check Use remote database. The default database name is TPCDB, but if you created a database with another name, enter it here. Enter the DB2 server’s host name in the Host name field. Enter the communication port number in the Port field. The default port number for DB2 is 50000. You also need to enter the path to the Java Database Connectivity (JDBC) driver. If your instance name is db2inst1, the default path is /home/db2inst1/sqllib/java.db2jcc.jar. You can enter the path directly or click Browse to search for it.


After you have selected your database connection information and completed this window, click Next. The Data server, Device server, Data agent, and Agent information window appears (Figure 3-181).

Figure 3-181 Data server information

9. If it is not already displayed, you must enter the fully qualified host name of the server where you are installing TotalStorage Productivity Center in the Data server name field. The default port of 9549 is listed in the Data server port field. You can change this port to suit your requirements, but we recommend that you do not change it. The adm group is listed by default in the TPC superuser field. We recommend that you do not change it.

10.If you want to perform advanced security role mapping, click Security roles. If you do, the Advanced security roles mapping window appears (Figure 3-182 on page 275).


Figure 3-182 Data server security roles mapping

11.You can optionally enter group names to map to each specific role in TotalStorage Productivity Center, which provides you with more customized control over your management environment. When you have finished entering the information in the window, click OK. The Data server information window appears.


12.If you want to discover Network Attached Storage (NAS) devices in your environment, click NAS discovery. The NAS Discovery Information (Optional) options window appears (Figure 3-183).

Figure 3-183 Data server NAS discovery options

13.You can add login information in the User name and Password fields in order to attach to Network Appliance storage devices. You can also add Simple Network Management Protocol (SNMP) community strings to search during the discovery process. To add an SNMP community, enter the community name in the SNMP community field and click Add. When you have completed this window, click OK. The Data server information window appears.


When you have finished making your selections, click Next. The Agent Manager information window appears (Figure 3-184).

Figure 3-184 Agent Manager information

14.Enter the fully qualified host name of the Agent Manager server in the Hostname or IP address field. The Port (secured) and Port (Public) fields are populated with the defaults of 9511 and 9513, respectively. We recommend that you do not change them. In the User ID field, enter manager. In the Password field for that ID, enter password. These values are the defaults and cannot be changed. The default agent registration password is changeMe. Enter changeMe or enter the agent registration password that you created during the Agent Manager installation into the final Password field. When you have finished entering the information in this window, click Next.


The summary information window appears (Figure 3-185).

Figure 3-185 Data server installation summary


15.Click Install. The Data server installation begins. A progress window appears (Figure 3-186).

Figure 3-186 Data server installation progress


16.When the installation completes, an installation results window appears (Figure 3-187).

Figure 3-187 Data server installation results

17.Click Finish to close the installer.

3.6 GUI for Web Access

You can configure the TotalStorage Productivity Center V3.3 user interface to be accessible from a Web browser. After you configure the TotalStorage Productivity Center V3.3 user interface to be accessible from a Web browser, a user can access the TotalStorage Productivity Center GUI by entering the URL, and the TotalStorage Productivity Center GUI applet is downloaded into the browser and executed. It looks and acts exactly as though it is on the native server. You can install the interface on any of the TotalStorage Productivity Center servers, management consoles, or workstations.

Note: If you are logging in to the TotalStorage Productivity Center GUI for the first time after installing the product and did not set up a IBM TotalStorage Productivity Center user role, you might not be able to log in. It is enough to create a user ID that is a member of the “adm” group.


3.6.1 Launch the TotalStorage Productivity Center GUIStart your Web browser (in our environment, we used Internet Explorer®), and enter the URL in order to open the Web GUI. By default, the URL to access the GUI is:

http://<host name>:9550/ITSRM/app/welcome.html

For example, if your host name for the TotalStorage Productivity Center server is fred.mycompany.com, the URL is:

http://fred.mycompany.com:9550/ITSRM/app/welcome.html

If you start the Web browser on your TotalStorage Productivity Center server machine, you can use localhost rather than the network name:

http://localhost

In our scenario we used:

http://Lead.itsosj.sanjose.ibm.com:9550/

See Figure 3-188.

Figure 3-188 TPC Web GUI start page


Java is a prerequisite for the Web GUI. You can verify its installation by running java -version, as shown in Figure 3-189.

Figure 3-189 Verifying Java installation

If you need to install Java, proceed with the installation for your platform. Follow the instructions to install Java.

After the Java installation completes, you can now access the TPC GUI using Java Web Start (Figure 3-174 on page 268). Click TPC GUI (Java Web Start). The window shown in Figure 3-190 will appear.

Figure 3-190 TPC GUI Java Web Start window

A security certificate approval window appears (Figure 3-191 on page 283). Depending on network transmission rates, it can take several minutes for the window to appear. At this point, you are prompted to start the TPC GUI. Click


Start. If you click Exit, the TotalStorage Productivity Center GUI does not load, and you have to reenter the TotalStorage Productivity Center GUI URL to restart.

Figure 3-191 Security Warning window

At this point, the Java applet for the TotalStorage Productivity Center GUI will download. The applet jarfile can take a while to load into your browser the first time. Be patient, because there is no progress bar displayed to indicate what progress is being made. After the applet jarfile has been loaded into your browser, it will remain in your browser cache until you dump it. Subsequent starts of the TotalStorage Productivity Center GUI load much faster.

After the applet has loaded, it launches the TotalStorage Productivity Center GUI. In the center of the GUI, the Sign-on window appears. It is prefilled with the Server address and access port (9549 for TotalStorage Productivity Center V3.3). Enter your TotalStorage Productivity Center server User ID and Password, and click OK to continue (Figure 3-192).

Figure 3-192 IBM TotalStorage Productivity Center Sign-on window


The TotalStorage Productivity Center GUI is displayed (Figure 3-193) and has all of the functionality of the native GUI on the TotalStorage Productivity Center server.

Figure 3-193 TotalStorage Productivity Center V3.3 GUI

3.7 Changing the agent configuration

If you have already installed the agent and later decide to change the Data Manager server to which it is registered, you can either uninstall the agent and reinstall it by specifying another server, or you can also change the server by performing the following manual actions:

1. Log on to the agent machine.

2. Add a file named PROBE_ME to the following directory:

– For Windows:

C:\Program Files\IBM\TPC\ca\subagents\TPC\Data

– For AIX and Linux:

/opt/IBM/TPC/ca/subagents/TPC/Data/


3. Edit the agent.config file in:

– For Windows:

C:\Program Files\IBM\TPC\ca\subagents\TPC\Data\config\

– For AIX and Linux:

/opt/IBM/TPC/ca/subagents/TPC/Data/config

Change serverHost= to your new Data Manager server name, as shown in Figure 3-194.

Figure 3-194 Editing agent configuration

4. Restart the Tivoli Common agent service:

– Linux and UNIX environment:

/opt/IBM/TPC/ca/endpoint.sh restart

– Windows environment, restart the following service:

“IBM Tivoli Common Agent-’C:\Program Files\IBM\ca’”

5. During the restart of Common agent, the program finds the PROBE_ME file and checks the Data Manager server name from the config file and registers itself to the new Data Manager server.


Chapter 4. Configuring IBM TotalStorage Productivity Center for Data

TotalStorage Productivity Center for Data is a powerful console for the storage environment that provides a set of policy-driven automated tools for managing storage capacity, availability, events, performance, and assets in your enterprise environment.

Data Manager can help you identify, evaluate, control, and predict your enterprise storage management assets. Because it is policy-based, it can detect potential problems and automatically make adjustments based on policies and actions that you have established.

This chapter provides a guideline for you to configure the TotalStorage Productivity Center for Data for your environment and obtain multiple reports for your environment.

4


4.1 Agent deployment optionsTotalStorage Productivity Center for Data receives almost all of the information that it provides in its reports and repositories solely through the Data agents on the managed servers and computers. It also relies on the presence of a Data agent infrastructure to perform policy driven management. Although TotalStorage Productivity Center for Data can also receive information directly from the storage subsystems through Common Information Model (CIM) agents without the presence of any Data agents, we recommend this approach only for very special requirements, because this approach limits the overall product capabilities to a large extent.

There are two ways of deploying the Tivoli Common agent and the TotalStorage Productivity Center Data agent: You can choose between local installation and remote installation. If you decide to use local installation, you can either install the agents interactively or perform a unattended (silent) installation. Remote installation can only be performed interactively.

4.1.1 Local installationLocal installation means that you have to be logged on to the computer on which you want to install the agent code. The TotalStorage Productivity Center Installer checks if there is a Tivoli Common agent already installed, and if not, installs this component.

The local installation process is provided either interactively by using a graphical user interface or in unattended (silent) mode. Unattended (silent) mode is useful in cases where you have to script the installation or where you simply do not have access to the GUI of the system (for example, telnet access only).

Local agent installation might be practical for a limited number of computers, but becomes rather elaborate and time-consuming as the number of managed computers grows.

4.1.2 Remote installationRemote installation is the process of pushing the agent code from a central computer over the network to any number of remote computers on which you want to install the TotalStorage Productivity Center agents. The TotalStorage Productivity Center Installer pushes the agent code to the target computers concurrently so that a large number of remote computers can be installed at one time. You can install all of the required agent components remotely, the Tivoli Common agent, as well as the Data agent. The supported operating systems for the target computers are Windows, UNIX, and Linux.


In a remote installation, the Tivoli Common agent is installed with the Data agent. The remote installation of the Data agent can be performed from any computer that is running one of the supported operating systems and that has a network connection to the remote target computers.

A remote agent installation is always interactive. Unattended (silent) remote installation is not supported at the time of the writing of this book. In the following sections, we guide you through both agent deployment methods.

4.2 Local installation of Data and Fabric agentsBefore you can install the Data agent, you have to verify that the TotalStorage Productivity Center Server and the Tivoli Agent Manager are installed, running, and can both be reached over the network.

For a successful installation, you have to provide the information summarized below:

� The host name or the IP Address of the Data server� The port to communicate with the Data server� The host name or the IP Address of the Device server� The port to communicate with the Device server � The host authentication password � The host name or the IP Address of the Tivoli Agent Manager server� The ports to communicate with the Tivoli Agent Manager server� The Common agent registration password

4.2.1 Interactive installationStart the TotalStorage Productivity Center Installer by running setup.exe on Windows systems and setup.sh on UNIX and Linux systems. You can locate these programs in the root directory of the installation CD. In the following windows, we show the dialog of an installation on a Windows platform. Data agent and Fabric agent are both installed at the same time. Of course, you can install either the Data agent or the Fabric agent separately.

Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 289

The steps are:

1. In the first window, select the preferred language for the installer (Figure 4-1).

Figure 4-1 Local interactive installation: Language selection

2. Click OK.

3. The International Program License Agreement is shown (Figure 4-2). Read the terms and select I accept the terms of the license agreement.

Figure 4-2 Local interactive installation: License Agreement

4. Click Next to continue.

5. In Figure 4-3 on page 291, you can choose the type of installation. We recommend that you always use Custom Installation when you install the agents. So, select Custom Installation by clicking the radio button next to it. In the window, you can also choose the installation path of the agents. The


default is C:\Program Files\IBM\TPC under Windows and /opt/IBM/TPC under UNIX and Linux. In our example, we keep the defaults.

Note that the installer not only installs files in the location that you specify in this window, but there are also files, such as ep.reg, ep.bak, and the guid directory installed to the C:\Program Files\Tivoli\ directory under Windows. In the Linux and the UNIX environment, the installer installs the ep.reg file, ep.bak file, and the guid directory under the /usr/Tivoli/ and /opt/tivoli directories.

Make sure that the installation location that you specify in this window is empty. Otherwise, the installer fails. Click Next to continue.

Figure 4-3 Local interactive installation: Type of installation and installation location


6. In the window shown in Figure 4-4, you must select which components of TotalStorage Productivity Center you want to install. Remove the check mark from all of the components except Data agent. Click Next to continue.

Figure 4-4 Local interactive installation: Component selection

7. Enter the following information in the next window (Figure 4-5 on page 293), and then click Next to continue:

– Data server name is the fully qualified host name or the IP address of the machine on which the TotalStorage Productivity Center Data server and Device server are running. At the time of the writing of this book, the Data server and the Device server have to be installed on the same machine, so the Data server name and the Device server name are always the same name. In our environment, the TotalStorage Productivity Center Server is on lead.itsosj.sanjose.ibm.com.

– Data server port is the port with which the Data agent communicates with the Data server. It is set when installing the Data server. We recommend that you keep the default port, which is 9549.

– Device server name is the fully qualified host name or the IP address of the Device server. In TotalStorage Productivity Center V3.3, it has to match the Data server name. In our environment, the name of the Data server and the Device server is lead.itsosj.sanjose.ibm.com.


– Device server port is the port with which the Fabric agent communicates with the Device server. It is set when installing the Device server. We recommend that you keep the default, which is 9550.

– Host authentication password is the password used by the Fabric agent to communicate with the Device server. Specify this password when you install the Device server.

8. Next, select options for the Data agent, as shown in Figure 4-5.

Figure 4-5 Local interactive installation: Server and agent settings

9. Click Data agent options.

10.In the window shown in Figure 4-6 on page 294, you can select two options:

– Agent should perform a scan when first installed

Remove the check mark by this option if you do not want to have the Data agent perform an initial scan of your computer after installation. This option is checked by default. We suggest that you accept this default, so that you make sure that your Data server gets a solid information base about your computer immediately after installation.

Note: When you install an agent on the TotalStorage Productivity Center server, you will notice that certain information, such as the Data server name, Data server port, Device server name, and Device server port are grayed out.


– Agent may run scripts sent by server

Remove the check mark by this option if you do not want the Data agent to be able to run scripts that the Data server sends. This option is checked by default.

The advantage of checking this option is that you can store scripts in the server’s \scripts directory, and you do not have to keep a copy of the script on every agent computer. When a script needs to be run on a particular agent, the server accesses the script from its local \scripts directory and sends it to the appropriate agent.

If the Agent may run scripts sent by server option is not selected, you must make sure that the script is stored in every agent’s \scripts directory.

Figure 4-6 Local interactive installation: Data agent setting

11.Click OK to continue, which brings you back to the window shown in Figure 4-5 on page 293. Click Next.

Note: If a script with the same name exists on both the server and the agent, the script stored on the agent takes precedence. This approach is useful if you want to run a special version of a script on one of your agents, while running another version of the same script across all of the other agents in your environment.


12.In the next window (Figure 4-7), you have to enter the fully qualified host name or IP address of the Tivoli Agent Manager, which must already be installed, up, and running. The Tivoli Agent Manager can run on the same machine as your TotalStorage Productivity Center Server or on a separate machine. In our environment, we have installed the Tivoli Agent Manager on the TotalStorage Productivity Center Server.

You also have to specify the ports, which the agents use to communicate with the Tivoli Agent Manager. They are specified during the installation of the Agent Manager. We recommend that you keep the default ports, which are 9511 (secure) and 9513 (public).

Finally, you have to enter the Common agent registration password, which is the password required by the Common agent to register with the Agent Manager. It is specified when you install the Agent Manager. The default password is changeMe.

Figure 4-7 Local interactive installation: Tivoli Agent Manager information


Note: If you do not specify the correct Agent Manager password, you are not allowed to continue the installation. You receive an error window and cannot continue until the correct password is entered.


13.The Common agent selection window appears (Figure 4-8). If a Tivoli Common agent is already running (for example, when you install a Fabric agent and a Data agent is already installed, or when you install a Data agent and a Fabric agent is already installed), you can choose to install your agent under the control of this Common agent by selecting it in the lower selection box. If a Common agent is not already installed on the system, you must select Install the new common agent at the location listed below and specify a location. The default location is C:\Program Files\IBM\TPC\ca under Windows and /opt/IBM/TPC/ca under UNIX and Linux.

Figure 4-8 Local interactive installation: Common agent options

14.If you click Windows Service Info in Figure 4-8, you get the Common agent service information window (Figure 4-9 on page 297). This information is optional. You can enter a Common agent service name, user ID, and password that the Installer uses to create a Windows service for the Common agent. Otherwise, by default, itcauser is created.


Figure 4-9 Common agent service name and user information

15.Enter the information and click OK, which will bring you back to the window shown in Figure 4-8 on page 296. Click Next.


16.The Summary Information window appears (Figure 4-10), where you can review the information that you have entered during the installation window.

Figure 4-10 Local interactive installation: Summary information window

17.Click Install to continue. The installer begins to install the Data agent (Figure 4-11 on page 299).


Figure 4-11 Local interactive installation: Installing the Data agent

Although you can cancel the installation while the progress bars are displayed, we strongly recommend that you do not. Cancelling the installation might result in an inconsistent state of your system.


Finally, a window appears announcing that the installation has finished successfully (Figure 4-12).

Figure 4-12 Local interactive installation: Installation complete

18.Click Finish to exit the installer.

4.2.2 Unattended (silent) installationFor an unattended (silent) installation of the agents, you have to set up a special response file for the TotalStorage Productivity Center Installer.

TotalStorage Productivity Center provides an example response file for the agent installation, which you can modify according to your environment. The name of this response file is setup_agents.iss, and it is located in the root directory of Disk 1 of the installation CDs.

There are variables for all of the information that you can supply during the interactive installation. They are summarized in Example 4-1.

Example 4-1 Local unattended installation response file variables

######################################################################## (C) Copyright Tivoli Systems, Inc. 2005.# 5608-VC0# All Rights Reserved# Licensed Material - Property of Tivoli Systems, Inc,


# an IBM company.# The source code for this program is not published or otherwise# divested of its trade secrets, irrespective of what has# been deposited with the U. S. Copyright Office.########################################################################## This option file is used to do silent installation of TPC components.## Data and Device Agents will be supported through this# silent installation options file.

## -options “setup_agents.iss” -silent#

######################################################################### Custom Dialog: License## The initial state of the License panel. The accept and reject option states# are stored as Variables and must be set with -V#

-V LICENSE_ACCEPT_BUTTON=”true”

######################################################################### Custom Dialog: License## The initial state of the License panel. The accept and reject option states# are stored as Variables and must be set with -V#

-V LICENSE_REJECT_BUTTON=”false”

######################################################################### IBM TotalStorage Productivity Center Install Location


## The install location of the product. Specify a valid directory into which the# product should be installed. If the directory contains spaces, enclose it in# double quotation marks. For example, to install the product to C:\Program Files\My# Product, use## -P installLocation="C:\Program Files\My Product"#

-P installLocation="C:\Program Files\IBM\TPC"

############################################################################################################################################### Dialog: dlgTPCProdInstallSel########################################################################### Create Database Schema

-V varCreateDBSchm="false"

######################################################################## Data Server Installation

-V varInstallDataSrv="false"

######################################################################### Device Server Installation

-V varInstallDevSrv="false"

######################################################################### GUI Installation

-V varInstallGUI="false"


######################################################################### CLI Installation

-V varInstallCLI="false"

######################################################################### Data Agent Installation

-V varInstallDataAgt="true"

######################################################################### Device Agent Installation

-V varInstallDevAgt="true"

################################################################################################################################################# Agent Manager Hostname

-V varAMHostname="lead.itso.sanjose.ibm.com"

########################################################################## Agent Manager Secured Port #

-V varAMRegPort="9511"

########################################################################## Agent Manager Public Port #

-V varAMPubPort="9513"

########################################################################## Common Agent Port


-V varCAPort="9510"

########################################################################## Common Agent Registration Password

-V varCAPassword="changeMe"

########################################################################## CA Installation Location

-V varCAInstallLoc="C:\\Program Files\\IBM\\TPC\\ca"

########################################################################## Common Agent Service Name (For Windows only)##-V varCASvcName=

########################################################################## Common Agent Service User ID (For Windows only)##-V varCASvcUsrID=

########################################################################## Common Agent Service User Password (For Windows only)##-V varCASvcUsrPW=

########################################################################## Whether to install New Common Agent if it does not exist.

-V varInstallNewCA="true"

#######################################################################


### Whether to use old Common Agent if it does not exist.

-V varUseOldCA="false"

########################################################################## Data Server Host Name.

-V varDataSrvName="lead.itso.sanjose.ibm.com"

########################################################################## Data Server Port Number.

-V varDataSrvPort="9549"

########################################################################## Device Server Host Name.

-V varDevSrvName="lead.itso.sanjose.ibm.com"

########################################################################## Device Server Port Number.

-V varDevSrvPort="9550"

########################################################################## Host Authentication password.

-V varHostAuthUsrPW="tpctpc"

########################################################################## Do Scan by Data Agent


##-V varDataAgtScan="true"

########################################################################## Run Scripts on Data Agent##-V varDataAgtScripts="true"

However, as with the interactive installation, most of the variables typically are used with their defaults and do not need to be changed when preparing the response file. Normally, you have to review at least the variables shown in bold in Example 4-1 on page 300 (for example, for a Linux system).

Also, you need to check that the target directory that you specify is empty. Otherwise, the unattended (silent) installation fails.

After modifying and reviewing the response file according to your needs, you can start the installer with the following command, executed from within the directory in which the response file is located:

� setup.exe -options “setup_agents.iss” -silent for Windows

� ./setup.sh -options “setup_agents.iss” -silent for Linux and UNIX

The installer exits with a return code, which can be used in your scripts. In addition, verify that the installation has completed successfully using the methods summarized in 4.4, “Verifying the installation” on page 320.

4.3 Remote installation of Data agents This section guides you through the necessary steps to perform a remote installation of the TotalStorage Productivity Center Data agent. You can only perform a remote installation interactively. At the time of the writing of this book, an unattended (silent) remote installation is not supported. You can perform remote agent installations to machines running either Windows (same domain or another domain), Linux, or UNIX operating systems.

If you were to install both a Data agent and a Fabric agent, you must install the Data agent before installing the Fabric agent to a remote computer. The Common agent is only installed with the Data agent. The remote installation of the Fabric agent requires that the Common agent is installed and running on the target computer. So, either install the Data agent first and then the Fabric agent,


or install both agents together. In the latter case, the TotalStorage Productivity Center Installer takes care of the proper sequence.

4.3.1 Preparing the remote installationBefore you can install the agents, you have to verify that the TotalStorage Productivity Center Server and the Tivoli Agent Manager are installed and running. You can install the Data agents from any workstation that has a network connection to the target machine.

For a successful installation, you need to know the following information:

� To remotely install the Data agents and Fabric agents, you must run the installation program on the computer that has the Data server and Device server.

� You must know the name or IP address of the computers on which you want to install the agent.

Before you remotely install an agent, remember the following items:

� You must install the Data agent before installing the Fabric agent to a remote computer. The Common agent is installed with the Data agent, and the Fabric agent requires that the Common agent be installed and running on the target computer. Install the Data agent first, and then install the Fabric agent.

� You must ensure that the computers on which you want to install the agent are available.

� When installing to a foreign Windows domain, the domain from which you are installing has to trust the foreign domains, and your login must be an administrator on the local computer (the computer from which you are installing) and a domain administrator on the foreign domains. Setting up the trust between domains is a complex task that must be done by your administrator before remotely installing Data agents.

� You must supply a user ID and a password that have administrative privileges on the target computer. The user ID must be a local administrative account on the target computer (not a domain administrative account).

� You need to know the fully qualified host name or the IP address of the computers on which you want to install the agents.

� You must know the host name or the IP Address of the Data server.

� You need to know the port to communicate with the Data server.

� You must know the host name or the IP Address of the Device server.

� You need to know the port to communicate with the Device server.

� You must know the host authentication password.


� You need to know the host name or the IP Address of the Tivoli Agent Manager server.

� You must know the ports to communicate with the Tivoli Agent Manager server.

� You need to know the Common agent registration password.

If you are installing a Data agent remotely on a Linux system, you must set the /etc/ssh/sshd_config file parameter PasswordAuthentication to yes.

To set the parameter, follow these steps:

1. Go to the following directory:

/etc/ssh

2. Use a text editor, such as vi, to edit the /etc/ssh/sshd_config file. Change the PasswordAuthentication parameter to yes.

3. Stop the daemon by running the following command:

/etc/init.d/sshd stop

4. Start the daemon by running the following command:

/etc/init.d/sshd start

If you are installing a Data agent remotely on a Solaris 10 system, you must set the following parameters in file/etc/ssh/sshd_config:

PasswordAuthentication yes PermitRootLogin yes

To stop sshd, you have to kill it; there is no stop command.

To start the sshd, enter:

/usr/lib/ssh/sshd

4.3.2 Performing the remote installationThe following steps show a remote installation that was performed from a Windows system to Windows (non-domain), AIX, and Linux computers. The installation dialog does not differ if the remote installation is performed from AIX or Linux. To invoke the remote installer, go to C:\TPCinstall on Windows and double-click setup.exe. On Linux or AIX, you go to the /TPCinstall/ directory and run setup.sh.

1. In the first window, select the preferred language for the installer (Figure 4-13 on page 309), and click OK.


Figure 4-13 Remote installation: Language selection

2. The International Program License Agreement is shown (Figure 4-14). Read and accept the terms by selecting I accept the terms of the license agreement.

Figure 4-14 Remote installation: License agreement



3. In the window shown in Figure 4-15, choose Custom Installation. Click Next to continue.

Figure 4-15 Remote installation: Type of installation and installation location


4. In the window shown in Figure 4-16, select which components of TotalStorage Productivity Center you want to install. We want to perform a remote installation of the Data agent, so remove the check mark from every component except Remote Data agent. Click Next to continue.

Figure 4-16 Remote installation: Component selection


5. In the next window (Figure 4-17), you only need to enter the Host authentication password, which is the password that is used by the Fabric agent to communicate with the Device server. You specify this password when you install the Device server.

All of the other information is already set correctly, because we are installing from the machine that is running the Data server and the Device server. Click Next to continue.

Figure 4-17 Remote installation: Server and agent settings


6. In the next window, Select the remote agents to install (Figure 4-18), enter the remote computers on which you want to install the Data agents and the Common agents (which are installed automatically together with the Data agent). You must enter the remote Linux and UNIX computers manually by host name or IP address. You can add Windows computers either manually or from the MS® Directory if you have an Active Directory environment.

Figure 4-18 Remote installation: Select remote computers


7. We want to enter our target computers manually, so we click Manually Enter Agents. The window in Figure 4-19 appears.

Figure 4-19 Remote installation: Manually add agents

8. In Figure 4-19, you have to enter the fully qualified host name or the IP address of the computer on which you want the Data agent and Common agent to be installed.

9. In our example, we added two remote systems individually because our target machines have different user IDs and passwords, as shown in Figure 4-20 on page 315.

Note: You can add multiple computers in this window if they share the same user ID and password. If computers do not share the same user ID and password, you must add them individually.


Figure 4-20 Remote Installation: List of remote computers to install the Data agent

10.When you are satisfied with your list of target computers, click Next.

Note: You can right-click a column name to filter or sort the listed computers. If you filter the names in the computer list, the computers that you selected for an agent installation that do not match the filter criteria do not appear in the list. Those agents are installed to the unlisted computers whose names do not match the filter.


11.The window shown in Figure 4-21 appears, where you can specify the settings for the Common agent Service on your Windows target machines. This information is optional. You can enter a Common agent service name, user ID, password, and a listener port that the installer uses to create a Windows service for the Common agent. Otherwise, itcauser is created and a random listener port is used by default. We recommend keeping those defaults. This window corresponds to the window shown in Figure 4-9 on page 297 for the local installation. Click Next.

Figure 4-21 Remote installation: Windows Common agent service settings

12.The TotalStorage Productivity Center Installer now runs a mini-probe on all of the computers that you selected in order to verify all prerequisites. The status for each computer changes several times. Finally, you see the window shown in Figure 4-22 on page 317.


Figure 4-22 Remote installation: Ready to install

13.In this window, the TotalStorage Productivity Center Installer shows you the default installation directory for each target computer.

Additionally in this window, you can also select two settings for the Data agents:

– Agent should perform a scan when first installed

Remove the check mark from this option if you do not want to have the Data agent perform an initial scan of your computer after installation. This option is checked by default. We suggest that you accept this default so that you make sure that your Data server gets a solid information base about your computer immediately after installation.

– Agent may run scripts sent by server

Remove the check mark from this option if you do not want the Data agent to be able to run scripts that the Data server sends. This option is checked by default.

The advantage of selecting this option is that you can store scripts in the server’s \scripts directory, and you do not have to keep a copy of the script on every agent computer. When a script needs to be run on a particular agent, the server accesses the script from its local \scripts directory and sends it to the appropriate agent.

If you do not check the Agent may run scripts sent by server option, you must make sure that the script is stored in every agent’s \scripts directory.


14.Click Install to continue.

The TotalStorage Productivity Center Installer starts to install the Data agents and the Common agent to the remote target computers. The installation status (Figure 4-23) is shown in the upper pane and you can monitor the installation log in the lower pane.

Figure 4-23 Remote installation: Progress

15.When completed, you see the status “Data Agent Started” for all successfully installed Data agents, as shown in Figure 4-24 on page 319.

Note: If a script with the same name exists on both the server and the agent, the script stored on the agent takes precedence. This approach is useful if you want to run a special version of a script on one of your agents while running another version of the same script across all of the other agents in your environment.

Note: You can review the Installation log for each computer by double-clicking the computer name or the IP address.


Figure 4-24 Remote installation: Installation complete

16.Click Done to continue (Figure 4-25).

Figure 4-25 Remote installation: Installation summary

The remote installation of the Data agent and the Common agent is now finished. The remote computers are now ready for the remote installation of the Fabric agents (if you choose to install them), because they now run a Common agent.


4.4 Verifying the installationAfter installing the server agents, check whether the agents have registered successfully with the TotalStorage Productivity Center Server. The agents register with the TotalStorage Productivity Center Server without any further discovery.

To check the communication between the TotalStorage Productivity Center Server and the agents, start the TotalStorage Productivity Center graphical user interface and log on.

In the Navigation Tree shown in Figure 4-26, select Administrative Services → Data Sources → Data Agents. Look for an entry for each of the newly installed agents on the right panel.

You now can click Check to see if TotalStorage Productivity Center Server can reach the agent and if the agent is up and running. In addition to this check, this window provides a view of the log files and the capability to perform administrative tasks, such as setting up a trace for each agent, reviewing logs, or even stopping and deleting an agent.

Figure 4-26 Verify agent installation


The install process creates a directory structure on the servers, which is similar to the directory structure shown in Figure 4-27 for a Windows server. For UNIX and Linux systems, the tree is created under /opt/IBM/ by default and otherwise looks the same.

Figure 4-27 Directory tree for Data and Fabric agent installation


Under Windows, you see one service, which is called IBM Tivoli Common agent (Figure 4-28).

Figure 4-28 Windows Service after agent installation

The Data agent and Fabric agent do not show up as a service. They run under the context of the Common agent.

Under UNIX and Linux, you see two processes. One process is the nonstop process, which launches the Common agent process, and the other process is the Common agent itself. The output of a ps -ef command shows the results in Figure 4-29.

Figure 4-29 UNIX and Linux process status after the agent installation


4.4.1 Log filesThe agent installation process creates a number of logs, which can be checked to retrace the installation process and also to monitor the activity during normal operation. These logs provide ample detailed information and are especially useful in the case of a failed installation in order to determine the reason for the failure and to troubleshoot the installation. They are spread over several locations.

Data agent logsThe following installation logs are for the Data agent when installed locally:

� <InstallLocation>\log\subagents\TPC\Data\install\ for Windows

� <InstallLocation>/log/subagents/TPC/Data/install/ for UNIX and Linux

The following installation logs are for the Data agent when installed remotely for Windows:

� <InstallLocation>\logs\

� <InstallLocation>\logs\install\

� <InstallLocation>\subagents\TPC\Data\log\

The following installation logs are for the Data agent when installed remotely for UNIX and Linux:

� <InstallLocation>/logs/

� <InstallLocation>/subagents/TPC/Data/log/


The following operational log is for the Data agent when installed locally for Windows:

<InstallLocation>\ca\subagents\TPC\Data\log\<host name>\

The following operational log is for the Data agent when installed locally for UNIX and Linux:

<InstallLocation>/ca/subagents/TPC/Data/log/<host name>/

Note: The default <InstallLocation> differs in local and remote administration.


The following operational logs are for the Data agent when installed remotely for Windows:


� <InstallLocation>\subagents\TPC\Data\log\<host name>

The following operational logs are for the Data agent when installed remotely for UNIX and Linux:


� <InstallLocation>/subagents/TPC/Data/log/<host name>

Common agent logsThe following installation and operational logs are for the Common agent when installed locally for Windows:

� <InstallLocation>\ca\logs\

� <InstallLocation>\ca\logs\install\

The following installation and operational logs are for the Common agent when installed locally for UNIX and Linux:

� <InstallLocation>/ca/logs/

� <InstallLocation>/ca/logs/install/

The following installation and operational logs are for the Common agent when installed remotely for Windows:


� <InstallLocation>\logs\install\

The following installation and operational logs are for the Common agent when installed remotely for UNIX and Linux:


� <InstallLocation>/logs/install/

4.5 Uninstalling the Data agentFor the Data agent, TotalStorage Productivity Center V3.3 offers you two methods of uninstallation: remote and local. The remote uninstallation procedure is independent of the installation method (local or remote).


The local uninstallation procedures differ slightly, depending on how the installation has been performed, because TotalStorage Productivity Center V3.3 uses different installers for remote and local installation.

The following sections guide you through the various uninstallation procedures.

4.5.1 Remote uninstallationYou can uninstall the Data agent remotely from the TotalStorage Productivity Center Server GUI. This method is only supported for the Data agent; the Fabric agent cannot be uninstalled remotely.

To uninstall the Data agent, start the TotalStorage Productivity Center graphical user interface and log on.

In the Navigation Tree shown in Figure 4-30, select Administrative Services → Data Sources → Data Agents.

Select an agent that you want to uninstall and click Delete on the right side of the window, and confirm your decision on the window that pops up to ask for confirmation by clicking Yes, delete the agents. This action erases the entry for the Data agent from the Data agent’s list and also uninstalls the Data agent on the remote computer.

Figure 4-30 Remote Data agent uninstall


4.5.2 Local uninstallationIf you have performed the installation of the Data agent and the Fabric agent locally, the local uninstallation of the Data agent, the Fabric agent, and the Common agent can be done in a single step.

In the following example, we show the uninstallation procedure for a Windows system where both a Data agent and a Fabric agent have been installed. This procedure applies if you only have a Data agent installed. There are no differences on UNIX or Linux systems in the dialog. The steps are:

1. To invoke the uninstallation on a Windows computer, select Start → Settings → Control Panel → Add/Remove Programs, as shown in Figure 4-31.

Figure 4-31 Local agent uninstall: Add or Remove Programs

2. Select TotalStorage Productivity Center and click Change/Remove.

Note: If you perform a remote uninstallation of the Data agent on a remote computer where no Fabric agent is installed, the remote uninstall process also uninstalls the Common agent; otherwise, the remote uninstallation process keeps the Common agent on the target computer.


3. On a UNIX or Linux machine, go to the directory /opt/IBM/TPC/_uninst/ and run the uninstall program. In the first window (Figure 4-32), select the preferred language for the uninstaller.

Figure 4-32 Local agent uninstall: Language selection

4. Click OK to continue.

You see the TotalStorage Productivity Center Installer Welcome window (Figure 4-33).

Figure 4-33 Local agent uninstall: Welcome window



In the window shown in Figure 4-34, select the components you want to uninstall. The TotalStorage Productivity Center Installer offers all of the components that it has detected on your system. In our example, the Data agent and the Fabric agent are installed, and we want to uninstall them both in one step.

Although there is a check box where you can select to force the uninstallation of the Common agent, it is not necessary to check this box, because the Common agent is automatically uninstalled when the last subagent is removed.

Figure 4-34 Local agent uninstall: Select component to uninstall


You see a summary of the components that TotalStorage Productivity Center Installer is about to uninstall (Figure 4-35 on page 329).


Figure 4-35 Local agent uninstall: Summary window



7. The system now uninstalls the selected components. Figure 4-36 appears when the uninstallation is finished. Note that a restart is necessary on a Windows machine. Click Finish.

Figure 4-36 Local agent uninstall: Uninstall complete

4.5.3 Remote agent uninstallationIf you have installed the Fabric agent and the Data agent remotely, you cannot uninstall both agents and the Common agent in one step. You have to uninstall the Fabric agent first and then uninstall the Data agent, which then uninstalls the Common agent also.


The steps are:

1. To invoke the uninstall on a Windows computer, select Start → Settings → Control Panel → Add/Remove Programs. You now see a separate entry for the Data agent. The uninstallation for the Fabric agent is invoked by selecting TotalStorage Productivity Center and clicking Change/Remove, as shown in Figure 4-37.

Figure 4-37 Local agent uninstall: Add or Remove Programs for remotely deployed agents


2. The uninstallation dialog is the same as described previously with the exception that the installer only offers you the option to uninstall the Fabric agent. You cannot select the Data agent (Figure 4-38).

Figure 4-38 Local agent uninstall: Select component to uninstall for remotely deployed agents

3. When the uninstallation of the Fabric agent is complete, you have to restart your system and again select Start → Settings → Control Panel → Add/Remove Programs.


4. Now, the TotalStorage Productivity Center entry is gone and you have to select TotalStorage Productivity Center for Data - Agent, as shown in Figure 4-39. Click Change/Remove.

Figure 4-39 Local agent uninstall: Add or Remove Programs for remotely deployed agents


5. Now another installer is presented, which is the installer that you used to perform the remote installation of the Data agent, as shown in Figure 4-40. Although there is a radio button, you cannot make a selection. Click Next.

Figure 4-40 Local agent uninstall: Uninstall of remotely deployed Data agent

6. A window (Figure 4-41 on page 335) appears where you can monitor the log of the uninstallation process in the lower pane.


Figure 4-41 Local agent uninstall: Uninstall of remotely deployed Data agent

7. When the uninstallation has finished, you finally see a window announcing the successful uninstallation of the Data agent (Figure 4-42).

Figure 4-42 Local agent uninstall: Uninstall of remotely deployed Data agent completed

8. Click OK, and restart your system.


4.6 Upgrading the Data agentThe TotalStorage Productivity Center graphical user interface allows you to upgrade your Data agent infrastructure from a central point of management. This central upgrade is only supported for the Data agent and the Common agent. You cannot upgrade the Fabric agent this way.

Before you upgrade your Data agents from your TotalStorage Productivity Center server GUI, you have to copy the upgrade.zip files of the new Data agent version for the operating systems you want to perform an upgrade for to the Total Storage Productivity Center Server install path:

� For Windows, the path is C:\Program File\IBM\TPC\data\upgrade.

� For Linux and UNIX, the path is /opt/IBM/TPC/data/upgrade.

Note that if you do not copy the upgrade.zip file, you break all of your agents.


The tree structure is similar to Figure 4-43.

Figure 4-43 Copy the upgrade.zip file to the server upgrade directories


Follow these steps to upgrade the Data agent:

1. After copying the necessary files to the respective directories, launch the TotalStorage Productivity Center graphical user interface and log on. In the Navigation Tree, select Administrative Services → Configuration and right-click Data Agent Upgrade, as shown in Figure 4-44.

Figure 4-44 Data agent upgrade: Create a Data agent upgrade job

2. On Figure 4-45 on page 339, which appears next, you can select the computers for which you want to perform a Data agent upgrade.


Figure 4-45 Data Agent upgrade: Create an upgrade job and select computers to upgrade

3. You can either select Computer Groups (if you have defined them in the TotalStorage Productivity Center) or select single computers or all computers, which have Data agents installed.

4. Verify that the Enable check box in the top right corner of the window is selected.

5. In the When to Run tab, you can specify if the upgrade runs immediately or is scheduled to run at a later time. The Options tab offers you options for the upgrade of the Data agents. You can specify if the Data agent will be overwritten if the server already has the upgraded level installed, and you can select the correct language option. In the Alert tab, you can choose which alerts the TotalStorage Productivity Center Server generates for the upgrade job.

6. After having reviewed all of the tabs, select File → Save. Specify a name for the job. The upgrade job is now saved and runs either immediately or at the time that you chose in the When to Run tab.


7. To check if the upgrades have completed successfully, right-click Data Agent Upgrades and select Refresh. You now see an entry for the upgrade job that you submitted. Click the small plus sign to the left of your job name and an entry with the time stamp of the submission of your job appears. Click this time stamp entry, and you see the log for the job on the right pane, as shown in Figure 4-46.

Figure 4-46 Data Agent upgrade: Job log of the upgrade job

8. You can now click the symbol next to the job log entry and examine the log for your upgrade job.


4.7 Alert disposition (SNMP and e-mail)Alerts can be redirected to event receivers in your environment. You can configure Simple Network Management Protocol (SNMP), Tivoli Event Console, and e-mail receivers.

To redirect alerts:

1. Select Administrative Services → Configuration → Alert Disposition (Figure 4-47 on page 342).

2. Enter the necessary fields that are available for your environment. Your event receivers need to have been configured in advance:

a. You can define two SNMP destinations or receivers. You must enter the community name and the host name. TotalStorage Productivity Center for Data uses the default port 162 if it is left blank.

b. For the Tivoli Event Console receiver, define the Tivoli Event Console server name. TotalStorage Productivity Center for Data uses the default port 5529 if it is left blank.

c. For the e-mail receiver, the following parameters are available:

• Mail Server: Name of the mail server in your environment.

• Mail Port: Port number for outgoing SMTP server. The default is 25.

• Default Domain: Default domain to use for sending e-mail.

• Return To: The e-mail address for undeliverable alerts.

• Reply To: The e-mail address if the user replies to an e-mail triggered by an alert.

• Data Administrator: The e-mail address for the notification of fatal server errors.

d. For alert log disposition, specify the number of days that you want Productivity Center for Data to keep alert records.


Figure 4-47 Configuration the Alert Disposition

3. Save to make the changes permanent.

4.8 Log file retentionYou can define how many runs or how long you retain logs in the Data Manager repository (Figure 4-48 on page 343) by doing these steps:

1. Select Administrative Services → Configuration → Log-file retention.

2. Define the following parameters:

– Maximum number of runs to keep of each schedule: Enter the number of runs that you want to keep for every scheduled job. The default is five runs.

– Maximum number of days’ worth of log files to keep (regardless of schedule): Enter the number of days that you want to keep log files regardless of schedules. The default is 90 days.


Figure 4-48 Log-File Retention

4.8.1 Quota and constraint e-mail address rulesIf a user exceeds the user’s quota or if the user violates a defined constraint rules, TotalStorage Productivity Center for Data triggers an alert to notify the user. You can configure the e-mail address of the user for the notification. The elements that you specify here are used to compose the e-mail addresses by the schema that you define here.

The steps are:

1. Select Administrative Services → Configuration → Quota and Constraint e-mail Address Rules (Figure 4-49 on page 344).

2. You can create an e-mail address based on the complete user name, lastname, firstname, or substring of these values or any predefined text.

3. You can add variables before or after the cursor position, edit, or delete any values that are highlighted:

a. To add variables, highlight the position and click Add After or Add Before. Select any of the following variables:

• USERNAME• LASTNAME• FIRSTNAME• Text• SUBSTRING of USERNAME,LASTNAME,FIRSTNAME

Tip: This combination of values defines parameters accordingly. If you define five days to retain log files and you are running scheduled jobs every day, even if you choose 10 runs, five of the runs are deleted.


b. To edit, highlight the variable that you want to edit and click Edit. You can edit only text variables.

c. To delete, highlight any variable and click Delete.

Figure 4-49 Composing the way that an e-mail address is formed


4.9 Scan/probe agent administrationYou can assign agents that perform the scan against the volume or filesystems of an Novell Directory Services (NDS) tree, NAS filers, and SAN Filesystems (SAN FSs). The window provides a complete list of:

� Licensed NetWare servers

� NetWare volumes that were discovered by TotalStorage Productivity Center for Data discovery jobs

� Licensed NAS filers

� Licensed SAN FSs

The steps are:

1. Select Administrative Services → Configuration → Scan/probe Agent Administration.

If you do not have a machine that contains Network Attached Storage (NAS) filers, an NDS tree, or a SAN FS, the window does not show you anything, and the rest of the steps are irrelevant for your environment.

2. You can either assign an agent to a single volume or to multiple volumes by highlighting the row or rows and by clicking Set Agent per row or Set agent for all selected rows.


3. The Filesystem Agent Editor window appears. Click the scan/probe agent drop-down list and assign an agent to a selected volume.


4.9.1 Manual NAS/NetWare server entryYou can manually enter information about the NetWare and NAS servers that you want to monitor. After adding it, you can assign an agent for the selected servers by using the procedure in the previous section.

To manually enter information about the NetWare and NAS servers that you want to monitor, follow these steps:

1. Select Administrative Services → Configuration → Manual NAS/NetWare Server Entry.


2. To add an NAS server, click Add NAS server (Figure 4-50):

a. A pop-up window appears. Fill in the parameters and click OK:

• Enter the network name of the NAS server.

• Select the operating system of the agent that gathers the information for the NAS server.

• Select the agent from the drop-down list.

• Specify the SNMP community. TotalStorage Productivity Center for Data uses the SNMP protocol to contact and identify an NAS filer.

• Specify the login ID and password to log on to the NAS filer, which is only valid for the Windows operating system.

Figure 4-50 Adding NAS server

b. TotalStorage Productivity Center for Data contacts the NAS filer and collects information from the NAS filer.

c. Now, you can access the Scan/Probe Agent Administration window and assign agents for the filesystem, as discussed in 4.9, “Scan/probe agent administration” on page 344.


3. To add a NetWare server, click Add NetWare server:

a. A pop-up window appears. Fill in the parameters and press OK:

• Select the NDS tree. NDS tree information is discovered by probe jobs that are run during agent installation.

• Enter the network name.

b. TotalStorage Productivity Center for Data contacts the NetWare Server and collects the volume or filesystem information of the NetWare server.

c. Now, you can access the Scan/Probe Agent Administration window and assign agents for the filesystem, as discussed in 4.9, “Scan/probe agent administration” on page 344.

4. To delete the information that you manually added, highlight the row and click Delete.

4.10 Configuring TPC communication to VMware

In this section, we detail how to configure TotalStorage Productivity Center for communication with a VMware ESX Server. The steps are:

1. Download the VMware Secure Sockets Layer (SSL) certificate. For communication, the VMware ESX Server and the VMware VirtualCenter Server use self-generated SSL certificates called rui.crt, which are located in the following directories:

– For the VMware ESX Server, the certificate is located in the directory /etc/vmware/ssl.

– For the VMware VirtualCenter Server, the certificate is located in:

C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL

Copy the certificate files from the VMware components to a directory on your local client machine.

2. Install these VMware certificates in a certificate store, which can be done on your local workstation. Afterwards, copy the truststore to your TotalStorage Productivity Center server. Use keytool on your local workstation to generate a certificate store/truststore. The keytool command is part of the Java Runtime Environment (JRE). If you work on Windows, locate keytool by running a search: Click Start → Search → All files and folders and search for keytool.*


Figure 4-51 shows an example of these search results.

Figure 4-51 keytool search results

Use a current version of keytool, such as the keytool.exe that is highlighted in Figure 4-51.

3. Create a certificate store/truststore. Use the keytool command to create the truststore. Figure 4-52 on page 349 shows the command syntax of the keytool command.


Figure 4-52 The keytool command syntax

The syntax to create the truststore for the TotalStorage Productivity Center server is:

keytool -import -file <certificate-filename> -alias <server-name> -keystore vmware.jks


In our environment, which is shown in Figure 4-53, the command is:

keytool -import -file rui.crt -alias faroe -keystore vmware.jks

Figure 4-53 Specifying the keystore password

The file from the VMware ESX server is named rui.crt. The VMware ESX Server in our environment is named FAROE. The truststore will be called vmware.jks. Enter a password for the keystore and enter yes to the question “Trust this certificate?”, as shown toward the end of Figure 4-53.

4. Truststores are located in the Device server configuration directory of your TotalStorage Productivity Center server at:

<TPC_install_directory>/device/conf

Copy the newly created certificate store/truststore to the Device server configuration directory of your TotalStorage Productivity Center server.

The truststore will automatically be defined at service startup time as the following property in the Device server Java virtual machine (JVM):

javax.net.ssl.trustStore System

5. Add the VMware Virtual Infrastructure (VI) data source (Figure 4-54 on page 351). The data source can be a hypervisor (ESX Server or VirtualCenter). This is the first step in getting information from VMware Virtual Infrastructure. Adding a VMware data source is similar to adding a Common Information Model (CIM) agent or Data agent. Select Administrative Services → Data Sources → VMware VI Data Source in your TotalStorage Productivity Center GUI and click Add VMware VI Data Source.


Figure 4-54 Add VMware VI Data Source

6. Test the connection to the VMware VI data source by clicking Test VMware VI Data Source connectivity (Figure 4-55) to ensure that you can access information from the VMware data source.

Figure 4-55 VMware connection status

7. After successfully connecting to the data source, run a discovery job for the VMware environment. The discovery is needed to retrieve every ESX Server instance that is part of the Virtual Infrastructure that has been added. The discovery mechanism is similar to a discovery for storage subsystems. Discovery jobs can be scheduled and are performed on the complete list of known VMware data sources.


Select Administrative Services → Discovery → VMware VI Data Source (Figure 4-56) and configure your VMware VI Data Source discovery. Run the discovery job now.

Figure 4-56 VMware: Data Source discovery

8. Run a probe job for the ESX Server, hypervisor, and virtual machines. This step will get the detailed information from the hypervisors and virtual machines for IBM TotalStorage Productivity Center. Select IBM TotalStorage Productivity Center → Monitoring → Probes and create a Probe for your VMware Hypervisor and Computers. For a total view of your VMware VI environment, you need the VMware VI Data Source and the Data agents running on the Virtual machines.

9. Configure alerts for VMware. You can create alerts for the following alert conditions:

– Hypervisor discovered– Hypervisor missing– Virtual Machine added– Virtual Machine deleted

Select Data Manager → Alerting → Hypervisor Alerts and right-click Hypervisor Alerts. Figure 4-57 on page 353 appears. Click Create Alert from the options menu that shows on the left of the window. Specify the alert details, and click Save to save your alert.


Figure 4-57 Create hypervisor alert

10.Install the Data agent on each of the virtual machines that you want to monitor. For full functionality, you need two data sources. The installation of a Data agent inside a VMware virtual machine is performed in the same manner as the installation of a Data agent on a physical server. Make sure that you have a platform that is supported by VMware and TotalStorage Productivity Center.

For more information about reporting and the topology view of the VMware server, refer to Chapter 5, “Operations and reporting” on page 379.

4.11 History aggregatorHistory aggregator runs in the Data Manager server and aggregates the data in the repository. You can configure the time that you want it to run. To set up the History Aggregator:

1. Select Administrative Services → Configuration → History Aggregator, as shown in Figure 4-58 on page 354.

2. In the When to Run tab, define the time and day of the week in which the job will run, for example, “Run at 03:30 AM on each day”.


Figure 4-58 Defining the time to run

3. In the Alert tab (Figure 4-59 on page 355), define the action if the aggregator job fails. You can set up the following alerts:

– Trigger an SNMP trap.

– Trigger a Tivoli Event Console (TEC) event.

– Send a message to the user when the user logs in to the system.

– Write an event to the Windows Event Log as a warning or an error.

– Run a predefined script on an agent machine.

– Send an e-mail to specified recipients.


Figure 4-59 Alert options

4. Check the Enabled box shown in Figure 4-57 on page 353 in the upper right corner of the window to make the aggregate job active.

5. Save to make the changes permanent by pressing Ctrl+s.

4.11.1 Data Manager NetWare tree loginsThe probe job discovers the NetWare servers in your environment during the Agent installation. In this window, you can edit the NetWare server login information. TotalStorage Productivity Center for Data uses this login data to contact the NetWare server and collect necessary information about the NetWare server. To edit the NetWare server login information:

1. Select Administrative Services → Configuration → NetWare Tree Logins.

2. Highlight the row and click Edit.

Note: You must have previously defined SNMP, Tivoli Event Console, or an e-mail server in order for the alert to successfully run.


3. You can edit the following information:

– Discovering agent: Select the agent from the drop-down list.

– Login ID: Specify a fully qualified user ID. This user ID must have permission to enumerate the volumes in the NetWare server and to scan any selected filesystem.

– Password: Specify the password of the login user ID.

4. Save to make the changes permanent by pressing Ctrl+s.

4.12 Data Manager CIMOM loginsData Manager can show storage subsystem capacity summary information and disk, storage group, and logical unit number (LUN) assets for storage devices. You need to install a Common Information Model Object Manager (CIMOM) agent that can communicate with each storage device that you want to manage and then configure that CIMOM agent in TotalStorage Productivity Center under Administrative Services → Data Sources → CIMOM Agents.

Data Manager server communicates with the CIMOM server using TCP/IP by using the HTTPS/HTTP protocol. If the CIMOM and Data Manager server are on the same network subnet, Data Manager can automatically find the CIMOM server during a discovery job. We describe the configuration later.

4.12.1 Configuring CIMOMsThere are two ways of making the CIMOMs of your infrastructure known to the TotalStorage Productivity Center. The method that you use depends on how you have set up your CIMOM infrastructure.

If all your CIMOMs and the TotalStorage Productivity Center Server are located in the same subnet or if you have your CIMOMs distributed across multiple subnets and have set up a valid Service Location Protocol (SLP) infrastructure utilizing SLP Directory Agents, you can discover all of your CIMOMs automatically. Otherwise, you have to enter CIMOMs manually.

We first try to do an automatic discovery to detect all CIMOMs, which are reachable through our SLP infrastructure. We then add the CIMOMs, which are still missing manually. To initiate an automatic CIMOM discovery, we select Administrative Services → Discovery and click CIMOM (Figure 4-60 on page 357).


Figure 4-60 Configuring CIMOMs: Initiate automatic CIMOM discovery (When to Run tab)

Next, we have TotalStorage Productivity Center perform a certain task or action. Many of these actions or tasks are handled as special objects within the TotalStorage Productivity Center called jobs, which are a major function of TotalStorage Productivity Center. We can define the jobs, run them, save them and run them at a later time, or schedule them for a single or repeated runs.

CIMOM discovery jobIn this example, we want the TotalStorage Productivity Center to discover CIMOMs, so we define a CIMOM discovery job:

1. Job definition works similarly for almost all types of jobs within TotalStorage Productivity Center. After selecting the Discovery → CIMOM job class in the Navigation Tree, you see three or more tabs in the Content Pane. In the first tab, the When to run tab, you can define a schedule for the job. You can have it run now, one time at a later time, or multiple times. In this scenario, we select to run the job right now (Figure 4-60).

2. The next tab, the Alert tab, allow specifying what to do when certain conditions for the job being defined arise at run time. For a CIMOM discovery job, there is only one condition for which you can define a reaction: You can specify what kind of Alerts TotalStorage Productivity Center triggers if the CIMOM discovery job fails.You will see these first two tabs in most job definitions.


Figure 4-61 below shows the Alert tab with the single condition for this job that we can choose, which is Job Failed.

Figure 4-61 Configuring CIMOMs: Initiate automatic CIMOM discovery (Alert)

3. In the last tab, which is the Options tab (Figure 4-62 on page 359), you can enter information that is specific for the type of job that you are currently defining. When defining a CIMOM discovery job, you can enter the IP addresses of the SLP Directory Agents of the environment that you want the discovery job to query for CIM Agents. In our case, we enter the IP address of the SAN Volume Controller (SVC) Master Console (ITSOSVC), which we have configured as a SLP Directory Agent.


Figure 4-62 Configuring CIMOMs: Initiate automatic CIMOM discovery (Enter DA addresses)

4. You have now entered all of the information that is needed by the CIMOM discovery job in order to run it successfully. We can now just save the job definition or save the job definition and have TotalStorage Productivity Center execute the job at the time that we have specified in the When to Run tab. To initiate the latter, we must click the Enabled check box in the upper right corner of the Content Pane and select File → Save in the menu task bar. We see a message box that states that the CIMOM job has been successfully submitted (Figure 4-63).

Figure 4-63 CIMOM Discovery Job submitted message


Now, let us see how this works, and how we can monitor our CIMOM discovery job.

Only one CIMOM job definition can exist in the system. We have defined this job definition in the previous steps and saved it. Every time that we select Administrative Services → Discovery → CIMOM, we can view and change this job definition.

This job definition can run multiple times. Each run produces an entry beneath the Administrative Services → Discovery → CIMOM node of the Navigation Tree. This design is for all types of jobs, and you see this design implemented throughout the TotalStorage Productivity Center user interface.

Because we have not only saved our CIMOM discovery job definition but have also started the execution of the job, TotalStorage Productivity Center has created an entry for your job.

Monitoring CIMOM discovery jobFollow these steps to monitor the CIMOM discovery job:

1. We can view this entry by selecting Administrative Services → Discovery → CIMOM, right-clicking CIMOM, and selecting Refresh Job List from the drop-down menu. Then, expand the CIMOM node of the Navigation Tree.

Important: The CIMOM discovery is designed as a two-stage process. First, the CIMOM discovery job locates all of the CIMOMs through the Service Location Protocol by broadcasting in its subnet and querying all SLP Directory Agents for which IP addresses have been entered in the job definition. In a second step, the discovery job tries to log into the CIMOMs that it has discovered and tries to retrieve information about the elements that are managed by each CIMOM.

Until this point, however, it was not possible to enter any user credentials for these logins. So, the discovery job uses null as a user ID and password to try to log into the CIMOMs, which is only successful for CIMOMs that have been set up to not require any user authentication. Therefore, it is highly likely that the first discovery job results in errors and with a status that the discovery and retrieval for the elements have succeeded only for few CIMOMs if any at all.

For the other CIMOMs, a second discovery job has to be initiated after entering the user credentials in order to retrieve the basic information for the elements behind those CIMOMs.


The entry for our job is named with the time stamp of its starting time. We see a small icon next to the entry. A blue circle indicates that the job is currently running. A red circle indicates that the job has completed with errors, and a green square indicates that the job has completed without errors. Also, TotalStorage Productivity Center uses a yellow triangle to indicate that a job has completed with warnings.

Figure 4-64 shows six entries. The upper entries belong to a job we ran earlier, and the last job listed is the job that we just submitted. The blue circle to the left of this entry indicates that the job is running.

2. If we click the entry of the job, we get a list of all of the logs for that job in the content pane. We can look at the logs by clicking the icon to the left of the log entry, which works even if the job has not yet finished but is still running.

Figure 4-64 Configuring CIMOMs: CIMOM discovery running


3. We can update the status of the job by right-clicking Administrative Services, selecting Discovery → CIMOM, and selecting Update Job Status. Note that the status does not update unless we refresh it this way. We finally see the window shown in Figure 4-65, which indicates that our discovery job has completed with errors.

Figure 4-65 Configuring CIMOMs: CIMOM discovery completed with errors

If we now examine the logs and we locate the failed part of the job, we learn that the errors are caused by failed logins, just as we expected. Note that the other parts of the jobs have completed successfully. These other parts are the logins and retrievals of information for the managed elements behind those CIMOMs, and these logins and retrievals do not require any authentication.

4. Next, we look at the CIMOMs that our discovery job has detected. We expand the Administrative Services → Data Sources → CIMOM Agents node of the Navigation Tree (Figure 4-66 on page 363). We now see an entry for each of the discovered CIMOMs. Those CIMOMs for which the login of the discovery job has been successful are marked by a green square and show SUCCESS for the connection status. Those CIMOMs for which no login can


be established are marked by a red circle and show the connection status LOGIN FAILED.

Our CIMOM Discovery job detected eight CIMOMs. The DS4500 CIMOM was discovered over two ports (secure and non-secure). For this CIMOM, the login has been successful, and the information for the elements that are managed by this CIMOM was retrieved. The information for the elements that are managed by the two other CIMOMs (the TS3500 - server on the linux3 server and the Brocade SMIAgent residing on the lead server) was also retrieved. The other CIMOMs require authentication; therefore, the login to those CIMOMs has not been successful, and TotalStorage Productivity Center cannot retrieve the information for the managed elements.

Figure 4-66 CIMOMs discovered using SLP by automatic discovery job

TotalStorage Productivity Center has now discovered three of our eight CIMOMs and was able to log in to one of those three CIMOMs.


User IDs and passwordsNow, the next task is to enter the user IDs and passwords for the CIMOMs, which are already discovered and need authentication:

1. We click the magnifying glass icon to the left of the CIMOM entry in the right pane of Figure 4-66 on page 363. Figure 4-67 appears, showing the information for the SVC CIM application programming interface (API). We can see all of the information that TotalStorage Productivity Center holds for the CIMOMs in the content pane. Enter the valid user ID and password as well as a display name.

We then use the magnifying glass icon to look at the detailed information for each of our discovered CIMOMs.

Figure 4-67 Configuring CIMOMs: Enter the CIMOM user ID, password, and display name

2. We save these entries by selecting File → Save in the menu task bar. Note that we have selected Test CIMOM connectivity before updating (Figure 4-67), which causes TotalStorage Productivity Center to connect to the CIMOM to try to log in to it with the credentials that we just have specified.


If this is login is successful, the status indication of the CIMOM turns green. However, TotalStorage Productivity Center does not retrieve the information about the elements that are managed by this CIMOM. This action requires another discovery job.

After updating all of our CIMOM definitions, we see the following window in Figure 4-68.

Figure 4-68 Configuring CIMOMs: Configuration of automated CIMOMs is complete


Manually entering CIMOMsNext, we have to enter the three missing CIMOMs manually:

1. Select Administrative Services → Data Sources → CIMOM Agents. Click Add CIMOM in the content pane (Figure 4-68 on page 365). TotalStorage Productivity Center shows us a window where you enter the basic information about the CIMOM (Figure 4-69):

– IP address, port, and protocol (HTTP or HTTPS) for the CIMOM

– Interoperability namespace (refer to the manufacturer of the CIMOM for the correct namespace. It is usually /root/ibm for IBM storage and tape systems). Refer to 2.9, “Interoperability namespace summary table” on page 66 for more information.

– User ID and password for the CIMOM (if required).

– Display name (optional).

Figure 4-69 Configuring CIMOMs: Add CIMOM dialog

2. After entering the requested information, click Save. The new CIMOM agent will be added to the CIMOMs list after TotalStorage Productivity Center verifies that the data that was provided is correct. We see the following CIMOM entries under Administrative Services → Data Sources → CIMOM Agents (Figure 4-70 on page 367).


Figure 4-70 Configuring CIMOMs: CIMOM configuration is complete

We have now completed the configuration of our CIMOMs in the TotalStorage Productivity Center. However, the retrieval of the information about the managed elements (storage subsystems, tape library, and switch) has not yet occurred for those CIMOMs that require authentication. So, we have to run a further CIMOM discovery job. This CIMOM discovery job does not discover any new CIMOMs (as long as we did not add any new ones to our infrastructure in the interim). However, the CIMOM discovery job is now able to log in into each of the configured CIMOMs and retrieve all information about the managed storage subsystems, tape libraries, and switches.

Note: The Brocade CIMOM and the Engenio Storage Management Initiative Specification (SMI-S) connect using HTTP and HTTPS over two separate ports, so each of them appears two times in the list.


This CIMOM discovery job now completes without errors and produces the output that is shown in Figure 4-71.

Figure 4-71 Configuring CIMOMs: Second CIMOM discovery job completed successfully

LogsWe now need to inspect the logs to verify that all of our storage subsystems, tape libraries, and switches have been discovered successfully.

We can also verify the discovery of a storage subsystem by inspecting the Alert Log. TotalStorage Productivity Center comes with a preconfigured default alert that raises an entry in the storage subsystem alert log each time that a new storage subsystem is discovered.

We can view this Alert Log by selecting IBM TotalStorage Productivity Center → Alerting → Alert Log → Storage Subsystem. Note that a SAN Volume Controller is not considered a storage subsystem in this context, so an alert for the discovery of an SVC is not generated by default.

TotalStorage Productivity Center also provides default alerts for the discovery of switches, fabrics, and endpoints.

We describe TotalStorage Productivity Center alerting in greater detail in 5.3.2, “Alerting” on page 428.


Now that we have successfully discovered all of our storage subsystems, tape libraries, and switches behind our CIMOMs, we can see if they appear in TotalStorage Productivity Center correctly.

4.13 Data Manager resource history retentionYou can specify how long you want to keep the history of data in the Data Manager repository. You have more information available for analysis if you keep the data for a long time; however, the longer you keep the data, the more space you will need for the repository.

To specify how long to keep the data:

1. Select Administrative Services → Configuration → Resource History Retention. See Figure 4-72.

2. Clicking the check box activates the value of the related line.

3. You can select to not keep the history by clicking No History or by removing the check marks from all of the check boxes.

4. To get the default values, click Use Defaults.

Figure 4-72 Retain history



4.13.1 Removed resource retentionThis window allows you to specify how long to keep information in the repository for values that are not in the system any longer. In other words, you can remove files from your system after the scan, and in the next scan, TotalStorage Productivity Center for Data identifies those files as removed. By using the parameter in the window that is shown in Figure 4-73, TotalStorage Productivity Center for Data keeps the files as long as you want.

To specify the removed resource retention period:

1. Select Administrative Services → Configuration → Removed Resource Retention. See Figure 4-73.

2. Select the appropriate check boxes to activate and adjust the value if needed.

Figure 4-73 Removed Resource Retention window


Note: Figure 4-73 shows elements that you will not have on your display if you only have Data Manager installed.


4.13.2 Resource history retention for databasesYou can specify how long you want to keep the history of data in the Data Manager repository for database tablespaces and tables. You will have more information for your analysis if you keep the data for a long time, but you will also need more space for the repository.

To set up the history retention:

1. Select Administrative Services → Configuration → Resource History Retention for Databases (Figure 4-74).

2. Clicking the check box activates the value of the related line.

3. You can select to not keep the history by clicking No History or by removing the check mark from all of the boxes.

4. To get the default values, click Use Defaults.

Figure 4-74 Retain History options window



4.13.3 Removed resource retention for databasesThis window (Figure 4-75) allows you to specify how long to keep information in the repository for values that are not in the system any longer. You can remove tables from your database after a scan, and in the next scan, TotalStorage Productivity Center for Data identifies those tables as being removed. By using the parameter in the window that is shown in Figure 4-75, TotalStorage Productivity Center for Data keeps the tables and tablespaces as long as you specified.

To specify the removed resource retention for databases:

1. Select Administrative Services → Configuration → Removed Resource Retention for Databases.

2. Click the check box to activate the value.

Figure 4-75 Retain removed databases


4.13.4 Adding databasesIn general, when an agent is registered to TotalStorage Productivity Center for Data, by default, it only reports its filesystem storage assets.

To use the database reporting of TotalStorage Productivity Center for Data as well, all agents, which are run for database reports, must be registered using the Databases portion of the License Key Editor.

If there are databases running that you want to monitor, you need to manually register your databases and then you can run jobs against your agents to report the databases. To register your databases:

1. Select Administrative Services → Configuration → License Keys.

2. Click the magnifying glass icon to the left of the line for IBM TPC for Data - Databases, as shown in Figure 4-76 on page 373.


Figure 4-76 License Keys for IBM TotalStorage Productivity Center for Data: Databases

3. In the Licensing tab, agents are displayed. Click the RDBMS Logins tab.

4. Initially, there are no entries for a computer. Click Add new.

5. The RDBMS Login Editor pop-up window appears (Figure 4-77 on page 374). Type in the values accordingly:

– For Oracle:

• Select the agent where Oracle runs.

• Enter the Oracle SID ID.

• Type the Oracle Host name.

• Specify the user name and password for TotalStorage Productivity Center for Data to log on to the Oracle database.

• The default port is 1521. If you installed Oracle by using another port number, contact your Oracle specialist to obtain the correct port number, and type the correct port number.

• Specify the Java Database Connectivity (JDBC) driver.

– For Microsoft SQL Server:

• Select the agent where the Microsoft SQL server runs. TotalStorage Productivity Center for Data only shows you agents that are on the Windows machine.

• Specify the instance of SQL server. If it is left blank, TotalStorage Productivity Center for Data uses the default instance.

• User name and password of the SQL server instance.

• The default port is 1433.

• Specify the JDBC driver.

– Sybase and IBM UDB DB2:

• Select the agent where Sybase or DB2 runs.

• Specify the instance or server name of Sybase and DB2.


• User name and password of the Sybase or DB2 instance.

• The default port for Sybase is 5000 and for DB2 is 50000.

Figure 4-77 RDBMS Login Editor window

6. Click Save to continue. TotalStorage Productivity Center for Data contacts the database immediately and registers the database to the TotalStorage Productivity Center for Data repository and also runs a probe job for the selected agent. Figure 4-78 shows two computers with databases running on them.

Figure 4-78 Database information

7. You can now edit or delete the database entry by highlighting the line and clicking Edit or Delete.

You can only change the user name, password, and port number.


4.13.5 Configuring chargebackIf you are running an IT infrastructure where you host multiple client environments, or if you just want to charge the departments in your own organization by monitoring their usage, you must configure chargeback. Follow these steps:

1. Select Data Manager for Chargeback → Parameter Definition (Figure 4-79).

Figure 4-79 Chargeback configuration

2. Select the output invoice format. There are two invoice formats that you can produce. One invoice format is the default format, which is the TotalStorage Productivity Center for Data format (Figure 4-81 on page 377), and the second invoice format is the standard Common Information Model schema (CIMS) format (Figure 4-82 on page 378).

3. You can charge your client or department by editing the following consumption values:

– Operating System Storage Usage by User. Output is based on users in your environment.

– Operating System Disk Capacity by Computer.

– Storage Usage by Database User.


– Total Size by Database-Tablespace.

4. To generate an invoice, select Online Execution in the Navigation Tree (Figure 4-80). Then, in the right pane, you have to provide information about where to create the output file, and then click Generate Output File.

Figure 4-80 Chargeback Online Execution

Figure 4-81 on page 377 and Figure 4-82 on page 378 show sample invoices generated with TotalStorage Productivity Center.


Figure 4-81 Chargeback sample invoice


Figure 4-82 Chargeback CIMS format


Chapter 5. Operations and reporting

In this chapter, we provide comprehensive information about using IBM TotalStorage Productivity Center for Data, with particular focus on its reporting capabilities. In the first part of this chapter, we show how to use exploit the product through the User Interface. In the second part, we show how IBM TotalStorage Productivity Center for Data has comprehensive reporting with more than 300 predefined reports, from system overview to detailed information. And finally, we provide a troubleshooting section.

5


5.1 OperationsThe Data Manager server is the major component of TotalStorage Productivity Center for Data. It uses a repository to accumulate all of the information about storage assets and how assets are used, filesystems, allocated files, and file characteristics, such as the size of the file, duplicate files, orphan files, obsolete files, and the backup information of these files. The Data Manager server has a powerful scheduler to submit several jobs, such as discovery, ping, probe, and scan.

In this section, we show you how to use the functions of Data Manager server through its graphical user interface (GUI).

5.1.1 The user interfaceThe Data Manager user interface consists of two primary components: The explorer-like tree view on the left and the panel on the right side, where all of the content is displayed.

Navigation TreeThe Navigation Tree appears on the left of the window, and you can expand, select, or collapse the tree. Figure 5-1 on page 381 shows several of the Navigation Tree elements that we discuss in this chapter. You can expand and collapse the necessary levels depending on the task on which you are working. Related functions are bundled in groups.


Figure 5-1 TotalStorage Productivity Center Navigation Tree

The primary groups of the Navigation Tree relating to TotalStorage Productivity Center for Data are:

� Administrative Services: Mainly used for configuration of TotalStorage Productivity Center for Data itself

� IBM TotalStorage Productivity Center

� Data Manager

� Data Manager for Database

� Data Manager for Chargeback

Each group is subdivided into functions:

� Administrative Services has the following sub-functions:

– Services: Used to view and control the various services that run in the Data Manager server.

– Data Sources: Used to control and view various agents/proxy components that are running on the monitored machines in your environment.

Chapter 5. Operations and reporting 381

– Discovery: Used to create, submit, and monitor Common Information Model Object Manager (CIMOM) discovery jobs.

– Configuration: Used to allow the system administrator to tune the settings that control various operational characteristics of Data Manager.

� IBM TotalStorage Productivity Center

– Configuration utility: Used to configure various operational characteristics of TPC.

– My Reports: Used to generate various reports.

– Topology: Topology Viewer to see high-level and detailed views of your storage assets and to perform monitoring, troubleshooting, and storage management tasks.

– Monitoring: It is used to define and run monitoring jobs regularly that collects information about resources in your enterprise.

– Alerting: The alerting feature enables you to define alerts for storage-related events that occur within your environment.

� Data Manager and Data Manager for Databases:

– My Reports: Used to generate and use reports easily.

– Monitoring: Used to monitor and run jobs.

– Alerting: Used to alert you when certain predefined conditions are met.

– Policy Management: Used to define policy within your environment, such as defining limits on the amount of storage, defining quotas, and defining acceptable file types.

– Reporting: Used to view information about your storage. More than 300 reports are available.

� Data Manager for Chargeback:

– Parameter Definition: Used for defining costs of using storage.

– Online execution: Used to create chargeback reports.

Content paneThe content pane appears to the right of the Navigation Tree pane. When you select functions from the Navigation Tree pane, a corresponding window appears in the content pane. You add, change, delete, create, and fill in the values by using functions in the content pane. Because the content of the content pane changes with the function that is selected, we show several content panes throughout this chapter (Figure 5-2 on page 383).


Figure 5-2 Content pane: Data agent example

5.1.2 Administrative servicesYou use this section of the Navigation Tree for administrative purposes (Figure 5-3). It allows you to monitor internal jobs, the status of components within Data Manager server, and the configuration of the server. We discuss in detail the four elements with which you can work.

Figure 5-3 Administrative services

Note: Refer to Chapter 4, “Configuring IBM TotalStorage Productivity Center for Data” on page 287 for all of the configuration details. We do not describe the configuration in this chapter.


ServicesWhen you expand Services and then click Data Server, you see the five services of the Data server (Figure 5-4).

Figure 5-4 Data Manager server and its five services

Data serverUnder Data Server, double-click Server and you see the following information for your Data Manager server in the content pane (Figure 5-5 on page 385):

� Server name� Port� Start time� Elapsed time� VM size� Network connections� Maximum connections� Pending requests� Processed requests� Database:

– JDBC URL– JDBC driver– DB connections– DB pool count

� Agents:– Total– Online– Offline– Unreachable– Upgrading– Upgrade required


Figure 5-5 Server Details under Services

The important values in this window are:

� Number of agents and whether they are offline, unreachable, or require an upgrade

� Number of pending requests

Under Data Server (Figure 5-4 on page 384), double-clicking Scheduler, GUI, or Agent gives you the following information:

� Service status� Pending requests� Processed requests� Idle threads


The important values in this window (Figure 5-6) are:

� Service status, which is active� Number of pending requests

Figure 5-6 Scheduler information

If you right-click the icon to the left of either the Scheduler, GUI, or Agent services, you see additional functions, as shown in Figure 5-7.

Figure 5-7 Additional functions

The additional functions, which are shown in Figure 5-7, include:

� View Log: All actions related to the service are written to the log. You can check the log to define the problem, to report the problem to the support center, and to check the status of the service, such as when it is started, initialized, or shut down. Errors are shown in the color red. If you are unable to see the logs, you can alternatively check the logs from the operating system:

– For the server component:

C:\Program Files\IBM\TPC\Data\log\server_xxxxxx.log

– For the Scheduler component:

C:\Program Files\IBM\TPC\Data\log\Scheduler_xxxxxx.log

– For CIMOM component:

C:\Program Files\IBM\TPC\Data\log\cimom_xxxxxx.log

– For the agent component:

C:\Program Files\IBM\TPC\Data\log\TPCD_xxxxxx.log

Figure 5-8 on page 387 shows a sample Scheduler log display in the content pane.


Figure 5-8 Scheduler Logs

� Configure tracing by right-clicking the desired service and selecting Configure Tracing (Figure 5-7 on page 386). When reporting a problem, you might be asked to produce a trace related to that service. In that case, enable the trace and provide the report to the support center for debugging. In this window (Figure 5-9 on page 388), you can enable the trace and define the trace level as DEBUG_MIN, DEBUG_MID, or DEBUG_MAX.

Figure 5-9 on page 388 shows the Configure Tracing pop-up window for the GUI and the Server. Note that the Server Tracing configuration also allows you to specify the number and the size of the trace logs.

The following example of the path and naming convention for the Trace log files is for the Server component:

C:\Program Files\IBM\TPC\Data\log\ServerTrace.log


Figure 5-9 Trace configuration

� The Shutdown function shown in Figure 5-7 on page 386 provides three options to shut down the service:

– Normal: Service is shut down cleanly. This option lets all running processes complete and accepts any new requests. Shutdown takes place if there is no new request and all of the running processes finish.

– Immediate: Service is shut down immediately. This option lets all running processes complete, but it does not accept a new request.

– Abort: All running processes are shut down without waiting for them to complete.

Data Sources Use the Data Sources node to view and control the various agents and entities that are running as part of your IBM TotalStorage Productivity Center environment. You can manage the following data sources using this node:

� CIMOM Agents � Data agents� Inband Fabric agents � Out of Band Fabric agents � VMware Virtual Infrastructure (VI) Data Source

For now, we only discuss the Data agents. Under Data agents (Figure 5-10 on page 389), you see all of the agents that are registered to the Data Manager server. If the agent is registered, it is monitored by the TotalStorage Productivity Center for Data.

Important: Always try to shut down the process by using the Normal or the Immediate option. To restart the service, right-click the service and select the Start option.


Figure 5-10 List of Data Agents

When you double click the particular Data Agent, you see high level information about that Data agent in the content pane. The information window has three tabs, General, Detailed and Jobs, which we describe in the following sections.


General tabThe following information is available under the General tab (Figure 5-11):

� Agent status� Port� Host Address� Last update� Time zone� Connection Errors� Consecutive Errors

The important values are the agent status and the errors.

Figure 5-11 Data Agent General Information


Details tabThe following information is available under the Details tab (Figure 5-12):

� Agent name� Host name� Host ID (This inclusion is new to TotalStorage Productivity Center V3.3.)� Start Time� Elapsed Time� VM Size� Manufacturer� OS Type� CPU Architecture� Job Count

Figure 5-12 Detailed agent information


Jobs tabIf there is any job that is currently running for this agent, you can see the following information, as shown in Figure 5-13:

� Schedule name� Job name� Run� Job Status� Scheduled time� Started time

Figure 5-13 Job details for a Data Agent

5.2 IBM TotalStorage Productivity Center menu reportsThis section gives an overview of the Data Manager functions under the IBM TotalStorage Productivity Center Navigation path. We will be covering Predefined reports, Batch Reports, Probe, and External Tool in detail throughout this section.

5.2.1 Predefined reports under the My Reports nodeSelect IBM TotalStorage Productivity Center → My Reports → System Reports → Data and expand the node, as shown in Figure 5-14 on page 393.


Figure 5-14 Predefined reports

Data Manager enables us to generate and use reports easily by using the predefined reports in the Navigation Tree entry titled My Reports. This section is divided into the subnodes discussed in the following sections.

System ReportsSystem Reports (Figure 5-14) are predefined in the TotalStorage Productivity Center and are prepared automatically for the monitored machines. In this section, we provide the steps to create the reports and summary information about the reports. We show examples of selected predefined reports.

When the reports are displayed in the content pane, you see either a pie chart icon, a magnifying glass icon, or both icons. Clicking the pie chart icon displays the report in a graphical pie chart form. Clicking the magnifying glass icon gives you the report details in a tabular form.

Note: We do not show all of the possible reports in detail in this section. For certain reports, we only provide a description of how to generate the report or a short description of the purpose of the report.


Access Time Summary reportThis report provides a summary of a number of files, depending on when they were last accessed, and it provides the following information about the files (Figure 5-15):

� The number and size of the files, which are accessed between several time periods

� Total number of files accessed

Figure 5-15 System access time reports

Complete the following steps to generate an Access Time Summary report for all of your servers:

1. Select IBM Total Storage Productivity Center → My Reports → System Reports → Data → Access Time Summary (Figure 5-16 on page 395).


Figure 5-16 Access Time Summary report

2. Click the Selection tab in the top left of the Report Filter Specifications.

3. Select the profile and columns to include or exclude and click Generate Report.

4. The first report is Network-wide, as shown in Figure 5-17.

Figure 5-17 Access Time Summary report: Network-wide


5. Click the pie chart icon to view the report in the pie chart format, as shown in Figure 5-18.

Figure 5-18 Pie chart of Access Time: Network-wide

To generate a report for an individual server, complete the following steps:

1. Select IBM Total Storage Productivity Center → My Reports → System Reports → Data → Access Time Summary.


3. Select the profile and columns to include or exclude and click Generate Report.

4. The first report is Network-wide. Click the magnifying glass icon to list the available servers, as shown in Figure 5-19 on page 397.


Figure 5-19 Access Time Summary: Network-wide servers

5. Click the magnifying glass icon or the pie chart icon to the left of a particular server to see the report for the selected server, as shown in Figure 5-20.

Figure 5-20 Pie chart report for an individual server

Disk Capacity Summary reportThis report shows the disk capacity of the servers. This report can give you the following information about the disk capacity:

� The total capacity of disks

� The amount of used space on disk


� The amount of free space on disk

� Raw volume space

� The amount of space used by Redundant Array of Independent Disks (RAID) or mirroring

You can generate a report by using the following steps:

1. Select IBM Total Storage Productivity Center → My Reports → System Reports → Data → Disk Capacity Summary.

2. Click the Selection tab in the top left of the Report Filter Specifications, as shown in Figure 5-21.

Figure 5-21 Disk Capacity Summary report: Report Filter Specifications

3. Select columns to include or exclude and click Generate Report.

4. The first report is Network-wide, as shown in Figure 5-22.

Figure 5-22 Network-wide Disk Capacity reports

5. Click the magnifying glass icon to see the report for all servers (see Figure 5-23 on page 399).


Figure 5-23 Disk Capacity Summary: By computer

Access File Summary report This report provides overview information about the files in the monitored servers. The following details are available:

� The total size of files� The number of files� The number of directories� Average size of files� The capacity of the filesystem

Storage Access Time reportThis report provides information about files that were last accessed. The following details are available:

� The name of the computer on which the file is stored� Several time periods when the file was last accessed

Disk Defects reportThis report provides disk defect information for the monitored servers. The following details are available:

� The name of the computer that has the disk defects� The number of defects detected� Disk revolutions per minute (RPM) � Capacity of disk and unallocated space� The number of recovered and unrecovered errors� Bytes written and read to disk


You can generate a report by completing the following steps:

1. Select IBM Total Storage Productivity Center → My Reports → System Reports → Data → Disk Defects, as shown in Figure 5-24.

Figure 5-24 Disk Defects report: Report Filter Specifications


3. Select columns to include and exclude and click Generate Report. The first report is network-wide.

4. Click the magnifying glass icon or the line chart icon next to each line to see the report for the selected server, as shown in Figure 5-25 on page 401.


Figure 5-25 Disk Defects report: By disk and computer

Storage Modification Times report This report provides information about files written within the network that were modified:

� Within the last 24 hours� Between one week to one month previous� Between one month to one year previous� More than one year previous

Most at Risk Files report This report shows files that have been modified but have not been backed up for a long time. Later, you can use this information to back up and archive the files automatically using Tivoli Storage Manager server. The following details are available:

� The name of the file, computer, and path name� The create, modified, and access date and time of the file� The owner of the file� The size of files (logical and physical)

You can generate this report by using the following steps:

1. Select IBM Total Storage Productivity Center → My Reports → System Reports → Data → Most at Risk Files.


2. Click the Selection tab in the top left of the Report Filter Specifications, as shown in Figure 5-26.

Figure 5-26 Most at Risk report: By computer

3. You can also select the computers from the list or perform filtering depending on the columns that are available.

4. The report shown in Figure 5-27 on page 403 shows you the oldest files, which have been modified but not backed up. The report is sorted by computer name.


Figure 5-27 Most at Risk Files report: By computer

5. You can also select the computers from the list or filter the information depending on the columns available.


Tivoli Storage Manager backup and archive from Most at Risk Files To initiate backup and archive to the Tivoli Storage Manager Server, perform the following steps:

1. Highlight the line or lines for each file. You can use the Shift key to select a group of files or the Ctrl key to select an individual file, as shown in Figure 5-28.

Figure 5-28 Select files to back up from Most at Risk Files report

2. Right-click and the Selection pop-up window appears (Figure 5-29 on page 405):

a. Select Create a new archive/backup job to run a new job.

b. Select Add to an existing archive/backup to add the list to an already created job.


Figure 5-29 Most at Risk report: Tivoli Storage Manager options

3. Select the type of backup that you want to run (see Figure 5-30):

– Archive– Selective backup (Full backup)– Incremental backup

Figure 5-30 Create File Archive/Backup Action


4. Define any extra option for the Tivoli Storage Manager server by selecting the appropriate tabs. Figure 5-31 shows the options under the When to Run tab, and Figure 5-32 on page 407 shows the Alert tab options.

Figure 5-31 When to Run tab options


Figure 5-32 Tivoli Storage Manager Create File Archive/Backup Action: Alert options

5. Press Ctrl+s to save or click Save to create the job.

6. You can follow the job status by selecting Data Manager → Policy Management → Archive/Backup → Job name.

Most Obsolete Files report This report provides information for files that have not been accessed or modified for a long time.

Oldest Orphaned Files report This report provides information for files that are not owned by any user. You can take a backup and archive of these files by using the same procedures that are mentioned in “Most at Risk Files report” on page 401.


User Quota Violations reportThis report provides information for users who have violated the quota defined by you (Figure 5-33). The following details are available:

� Quota creator� Quota name� User who violated the quota� Space used by user that exceeds the quota

Figure 5-33 Quota violations

Storage Availability report This report provides information about the availability of computers that are monitored using the ping job.

Storage Capacity report This report provides storage capacity information about each computer, as shown in Figure 5-34 on page 409.

Tip: You need to define the quota in advance in order to have reports for quota violation. Our quota example was set up in Data Manager → Policy Management → Quotas → User → Computer. No data is displayed if there is not a quota defined or if there are no violations.


Figure 5-34 Disk capacity

Total Freespace reportThis report provides the amount of unused storage capacity in your environment.

User Space Usage reportThis report provides storage usage based on user on the server and storage capacity information about each computer.


Wasted Space reportThis report provides information about storage used by files, which are not owned by an operating system and have not been accessed for one year, as shown in Figure 5-35.

Figure 5-35 Wasted space summary

5.2.2 Batch reportsThe batch reporting feature enables you to run any report on a regularly scheduled basis. This feature enables you to conveniently run reports and gather data on a set schedule.

To create the batch report, perform the following steps:

1. Select IBM Total Storage Productivity Center → My Reports → Batch Reports.

2. Right-click and select Create Batch Report, as shown in Figure 5-36.

Figure 5-36 Batch report options


3. Select the report type, as shown in Figure 5-37. You can select the following reports:

– Asset System-wide– Storage Subsystems– Availability– Capacity– Usage– Usage Violations– Backup– Groups

Figure 5-37 Batch report types


4. Click the Options tab to define the batch output, as shown in Figure 5-38. The options include:

– Select Agent computer to run the batch report job.– Select output format:

• Comma separated value (CSV)• Formatted File• HTML File

Figure 5-38 Batch report options

– Select the format for the output file name (see Example 5-1).

Example 5-1 Batch report format

{Report creator}.{Report name}.{report run number}TR50411.batch-report1.001.HTML

5. Click the When to Run tab to define the schedule time.

6. Press Ctrl+s to save the batch report. The job will be submitted at the specified time and day. You can follow the status by selecting Data Manager → My Reports → Batch Reports.


7. The batch report output is saved to the specific directory of the agent machine with the name that you specified in the Options tab:

– For Windows, the output is saved in:

\Program Files\IBM\TPC\ca\subagents\TPC\Data\log\<computername>\reports\

– For UNIX, the output is saved in:

/opt/IBM/TPC/ca/subagents/TPC/Data/log/<computername>/reports/

5.2.3 ProbeProbe jobs collect detailed statistics about all of the assets of the managed infrastructure, such as computers, disk controllers, hard disks, clusters, fabrics, storage subsystems, logical unit numbers (LUNs), virtual machines, tape libraries, and filesystems. Probe jobs can also discover information about new or removed disks and filesystems. Probe jobs can be directed against any elements in the managed infrastructure. In our examples, we run probe jobs against storage subsystems, fabrics, and computers.

To create the probe job, complete the following steps:

1. Select IBM Total Storage Productivity Center → Monitoring → Probes.

2. Right-click and select Create Probe.

3. You can select what to probe, such as a computer, computer groups, clusters, storage subsystem groups, or storage subsystems.

4. You can create separate probe jobs for various groups.

5. Select job schedule characteristics, such as run immediately, run once at a certain time, or run several times.

6. Save to create the probe job.

7. You can follow the status of the probe job by selecting IBM Total Storage Productivity Center → Monitoring → Probes → probe-job-name → date-time-of-run.


Figure 5-39 shows all of the elements of the probe job in one window.

Figure 5-39 Create a probe job

5.2.4 External ToolsThe External Tools node in the IBM TotalStorage Productivity Center Navigation Tree provides a simple way to configure and launch the IBM TotalStorage Productivity Center for Replication GUI, and other Web GUIs or local executables, from within IBM TotalStorage Productivity Center.

One external tool, IBM TotalStorage Productivity Center for Replication GUI, is auto-configured during Data server startup if the IBM TotalStorage Productivity Center for Replication is running on the same host as the IBM TotalStorage Productivity Center for Data. It can also be configured manually.


If you have installed IBM TotalStorage Productivity Center for Replication on a different system, follow the below steps to configure TotalStorage Productivity Center main GUI:

1. Right-click IBM TotalStorage Productivity Center → External Tool, as shown in Figure 5-40.

Figure 5-40 Adding TPC-R Server to TPC GUI

2. Enter the Hostname/IP address of the TPC-R server, as shown in the Figure 5-41and click save.

Figure 5-41 Adding TPC-R server to TPC GUI


3. Click the Launch button to launch the IBM TotalStorage Productivity Center for Replication from the IBM TotalStorage Productivity Center GUI, as shown in Figure 5-42

Figure 5-42 Launching the TPC-R from TPC GUI

4. The external tool is added under IBM TotalStorage Productivity Center → External Tools → Label, where <Label> is the definition in the Label field.

5.3 Data Manager menuNow that we have reviewed the first part of the Data Manager function, which is located under the IBM TotalStorage Productivity Center node in the Navigation Tree, we can scroll down to the Data Manager node. These are the functions in the Data Manager Main Menu, as shown in Figure 5-43 on page 417.


Figure 5-43 Data Manager main menu

5.3.1 MonitoringThe monitoring function enables us to run regularly scheduled or one-time data collection jobs. These jobs gather statistics about storage assets and usage within the environment. You can use the information gathered by monitoring jobs to set alerts, enforce policies, and generate detailed reports.

Determining what information you want to gather about your storage resources is critical to helping you implement a storage management strategy. Once you have determined the types of information you want to collect about your storage resources, you can use monitoring jobs to collect that information according to a schedule that you define.

Storage resources that Data Manager can collect information about includes computers, clusters, disk controllers, hard disks, NAS Filers, and filesystems. The data and statistics gathered by monitoring jobs are stored in the database repository and are used to supply the data necessary for reports.

The following sections give a detailed description of the sub-menus under Monitoring.


Groups A group represents a set of user-defined objects against which you can run monitoring and reporting jobs. It enables you to define a set of related objects one time and save these selections as a named group for future use in scans, pings, and other entities within the Data Manager. This section describes the possible groupings.

� Computer: A computer group is a logical grouping for related computers. A computer can belong to one computer group only. A computer will automatically be removed from a group if you add it to another group.

Use computer groups to monitor computers that are related to each other or belong to a common group such as a department, a location, a territory, and so on. To create a computer group, perform the following steps:

a. Select Data Manager → Monitoring → Groups → Computer.

b. Right-click and select Create Computer Group. All available computers are listed.

c. Double-click a computer to add a computer to the group under Current Selections.

d. Press Ctrl+s to save the group with a new name. A pop-up window asks for the name of the group (Figure 5-44). Enter the computer group name and press OK.

Figure 5-44 Grouping computers

� Filesystem: The filesystem group is a grouping of filesystems in computers. A filesystem can belong to one filesystem group only. A filesystem will automatically be removed from a group if you add it to another group. To create the filesystem group, perform the following steps:

a. Select Data Manager → Monitoring → Groups → Filesystem.


b. Right-click and select Create Filesystem Group. The list of available computers and their filesystems appears.

c. Expand the computer name to display the filesystem names (Figure 5-45).

d. Double-click the filesystem name to include in the group.

e. Press Ctrl+s to create and save the group.

Figure 5-45 Grouping filesystems

� Directory: A directory group is the grouping of directories in computers. You can include a directory in multiple directory groups. To create the directory group, complete the following steps:

a. Select Data Manager → Monitoring → Groups → Directory.

b. Right-click and select Create Directory Group.

c. Click New Computer.

d. The Edit directories for computer pop-up window appears.

e. Select the computer or all computers.

f. Edit the directory name and click Add.

g. For another directory’s information, repeat Steps 3 to 6.

Important: TotalStorage Productivity Center for Data does not check the syntax or whether the directory is available. Be careful that you add directories that are actually available; otherwise, the group reports for the groups do not contain any data.


h. Each time that you add a directory for a computer, the computer’s information does not display on the next Edit directories for computer window. To add a new directory to the computer, you must perform the following steps:

i. Right-click the computer name and select Edit. The Edit directories for computers pop-up window appears for the selected computer.

ii. Add a new directory and press OK.

i. When all of the directories are added, press Ctrl+s to save the grouping information (Figure 5-46).

Figure 5-46 Grouping directories

� User: This function groups users on all computers. A user can belong to one user group only. To create a user group, perform the following steps:

a. Select Data Manager → Monitoring → Groups → User.

b. Right-click and select Create User Group. All available users are listed.

c. Double-click a user to add a user to the group under Current Selections.


d. Press Ctrl+s to save the group with a new name. A pop-up window asks for the name of the group (Figure 5-47). Enter the user group name and press OK.

Figure 5-47 User group creation window

� OS user group: The OS user group is a grouping of users that is defined in the operating system as a user group. We can create OS User Groups in the same way as we created the User Group above.

Ping jobsThe Ping job collects information about the availability of the storage assets in your environment. By running pings and viewing the results of those pings in Reporting → Availability reports, you can monitor and report on the availability of your storage, both from a network point of view and from a computer uptime perspective.

To create the Ping job, complete the following steps:

1. Select Data Manager → Monitoring → Pings.


2. Right-click and select Create Ping. You can add a computer, computer groups, or clusters for the Ping job to run against (Figure 5-48).

Figure 5-48 Create a Ping job

3. You can create separate Ping jobs for multiple groups, for example, one Ping job for computers that have DB2 and one Ping job for Linux computers.

4. Select job schedule characteristics, such as run immediately, run once at a certain time, or run several times at regular intervals.

5. You can also set up alerts for triggering an action like SNMP traps, running a script, sending an e-mail, and so on, when a certain condition is met. The default setting is Computer Is Unreachable More Than certain number of times. No other alerting conditions are currently available.

6. Press Ctrl+s to create and save the Ping job.

7. You can follow the status of the Ping job by selecting Data Manager → Monitoring → Pings → ping-job-name → date-time-of-run. See Figure 5-49 on page 423.


Figure 5-49 Ping job status

ScansThe Scan job collects statistics on the usage of storage. Detailed usage information is stored in the Data Manager repository and we can see those details in the form of reports. To create the Scan job, perform the following steps:

1. Select Data Manager → Monitoring → Scans.


2. Right-click and select Create Scan. You can add filesystems, a computer, computer groups, or clusters to the Scan job, which runs as shown in Figure 5-50.

Figure 5-50 Create a Scan job

3. You can add specific directories to the Scan job:

a. Click the Directory Groups tab.

b. Select the Available Directory Groups or create one by clicking New Directory Group.

c. Click New Computer.

d. A pop-up window appears. Select the computer name from the list, add the directory for the selected computer, and click Add.

e. Click OK and save the directory group by pressing Ctrl+s.

4. Select the Profile tab to customize the Scan job, as shown in Figure 5-51 on page 425. Select the profiles according to the requirements.


Figure 5-51 Scan job Profiles selection

5. Click the When to Run tab to select job schedule characteristics, such as run immediately, run once at a certain time, or run several times.

6. You can also set up alerts for triggering an action like SNMP traps, running a script, sending an e-mail, and so on, when a certain condition is met. The default condition is Scan Failed. No other condition is available so far.

7. Save to create the scan job.

8. You can follow the status of the scan job by selecting Data Manager → Monitoring → Scans → scan-job-name → date-time-of-run.


ProfilesProfiles enable you to define which statistical information you plan to gather during the Scan. TotalStorage Productivity Center for Data comes with a predefined set of profiles. You can find the information about default profiles in Table 5-1.

Table 5-1 List of profiles

Profile name Description

Most At Risk Statistic about the number of files that are modified (longest) but not backed up since they were modified (the default is 20 files) (Windows only).

By Access Statistics about the file based on its access time.

By Creation Statistics about the file based on its creation time (Windows only).

By Mod Not Backed Up Statistic about files that are modified but not backed up since the modification (Windows only).

By Modification Statistics about files by the length of time since the last modification.

File Size Distribution Information about the size of the files.

Largest Directories Statistics for a certain number of the largest directories (the default is 20 directories).

Largest Files Statistics for a certain number of the largest files (20 files are the default).

Largest Orphans Statistics for a certain number of the largest orphan files. Orphans are the files that have no owner since the time that they were created (the default is 20 files).

Most Obsolete Files Statistics for a certain number of the most obsolete files. Obsolete files are files that have not been modified or accessed for a long time (the default is 20 files).

Oldest Orphans Statistics for a certain number of the oldest orphans (the default is 20 files).

Summary By File Type Summary based on file type.


You can also define your own profiles. To create a user-defined profile, perform the following steps:

1. Select Data Manager → Monitoring → Profiles.

2. Right-click and select Create Profile.

3. In the Statistics tab, you can define several options for the files that will be included in the Profile (Figure 5-52 on page 428):

a. Summary space usage by:

– Filesystem– Owner– Group– File types

b. Gather statistics by length of time since:

– Last access– Creation– Last modification– Last modification (not backed up)

c. Gather information about the:

– Size of the distribution– Largest file– Largest directories– Most obsolete files– Most at risk files– Largest orphaned files– Oldest orphaned files

4. Optionally, define the number of files about which to gather information.

Summary By Filesystem/Directory Summary based on filesystem/directory.

Summary By Group Summary based on groups.

Summary By Owner Summary based on owner.

Temporary Files Statistics for files that are not owned by the operating system and have not been accessed in one year.

Wasted Space Statistics for space usage for space that is not owned by the operating system and that has not been accessed in one year.

Profile name Description


Figure 5-52 Creating Profiles

5. Press Ctrl+s to save and create the Profile. Continue to use these windows if you want to create more profiles with your own definitions.

5.3.2 AlertingAlerting is used to inform the TotalStorage Productivity Center administrator when certain conditions occur on the devices that are monitored. TotalStorage Productivity Center for Data collects statistics for the computer, storage subsystems, filesystems, directories and VMware ESX Server. You can set certain thresholds to detect the problem or events that might create problems later, so that storage administrators can be proactive to correct potential problems. Once you have defined the events or conditions for which you want to be alerted, you can let Data Manager monitor your storage so that you do not have to.

We can define four types of alerts under Data Manager. The four types of alerts are Computer Alerts, Filesystem Alerts, Directory Alerts, and Hypervisor Alerts.


Computer alert conditionsYou can use these alerts to monitor computers for any changes in configuration or status. When a condition is detected during a probe, an alert is generated. Computer alerts can be applied to computers, computer groups, and clusters.

To create a computer alert, do these steps:

1. Select Data Manager → Alerting → Computer Alerts.

2. Right-click and select Create Alert, as shown in Figure 5-53.

Figure 5-53 Create an alert

3. The next window, which is shown in Figure 5-54, is the Create Alert window where you define your alert.

Figure 5-54 The general Create Alert window


4. When you select the Alert tab, you can use the Triggering Condition drop-down list to select one of the alert types shown in Figure 5-55.

Figure 5-55 Select an alert type that you need

5. In the Triggered Actions area, select the actions that will occur as a result of the triggering condition.You can trigger SNMP Trap, TEC Event, Login Notification, Windows Event Log, Run Script, or Email.

6. After you have selected the type of alert and the action on alert, select the Computers tab to associate the alert to one or more of your resources, as shown in Figure 5-56 on page 431.


Figure 5-56 Always make an association with a resource

7. Press Ctrl+s to save the alert.

These alert conditions might be detected by a probe job. The following predefined alert conditions are available. Note that this list is subject to change and might be incomplete or might contain extra entries:

� RAM increased� RAM decreased� Virtual memory increased� Virtual memory decreased� New disk detected� Disk not found� New disk defect found� Grown disk defect found� Disk failure predicted� New filesystem detected� Virtual server added� Virtual server removed� Virtual server moved� Computer Unreachable� Computer Discovered


� Computer Status Change Offline� Computer Status Change Online� Computer Property Change� Host bus adapter (HBA) Driver Version Change� HBA Firmware Version Change� Cluster Resource Group Added� Cluster Resource Group Removed� Cluster Resource Group Moved

The above Cluster Related Alert Conditions are only for HACMP on AIX. The steps to create the alert for HACMP is same as a regular one.

You can select only one condition at a time. If you want to detect several conditions, you must define a separate alert for each condition.

Filesystem alertsYou can use these alerts to monitor filesystems for available free space, changes in configuration, or if a filesystem being removed or unmounted. These alerts are detected by the Scan job.When the condition is detected during a scan, an alert is generated. Filesystem alerts can be applied to filesystems, filesystem groups, computers, computer groups, and clusters.

The following predefined alerts are available:

� Filesystem not found

� Filesystem reconfigured

� Filesystem freespace less than X (percentage, KB, MB, or GB)

You have to enter a threshold value for this condition.

� Free UNIX Filesystem (FS) Inode less than X (percentage or inodes)


As an example, let us define an alert for Filesystem Freespace less than 30 percent. Complete the following steps to create the alert:

1. Select Data Manager → Alerting → Filesystem Alerts.

2. Right-click and select Create Alert.

3. Select Filesystem Freespace less than from the condition list (Figure 5-57 on page 433).

4. Enter 30 for the Value and select percent from the Value Units drop-down list.

5. Select a triggered action to occur when the condition is met. We select Windows Event Log and the Warning type.

6. Click the Filesystems tab and select which machines to notify.



Figure 5-57 Creating filesystem alerts

Directory alertsYou can use these alerts to be notified when either a directory is not found or a directory consumes more than a specified amount of storage space. These alerts are detected by the scan job. When a condition is detected during a scan, an alert is generated. These alerts can be applied to directories and directory groups.

The following predefined alerts are available:

� Directory not found.

� Directory consumes more than X (percentage, KB, MB, or GB).


As an example let us define an alert for a directory consuming more than 2 GB. Complete the following steps to create the alert:

1. Select Data Manager → Alerting → Directory Alerts.

2. Right-click and select Create Alert.

3. Select Directory Consumes More Than from the condition list.


4. Enter 2 for the value and select Gigabytes from the list (Figure 5-58).

5. Select a triggered action to occur when the condition is met. We have selected Windows Event Log and the Warning type.

6. Select the directories for which you want to set alerts.


Figure 5-58 Creating directory alert

Hypervisor alertsThe latest version of TPC has a new alert feature for VMware ESX Server. The following alert conditions are supported for VMware ESX Server:

� Hypervisor Discovered� Hypervisor Missing� Virtual Machine Added


� Virtual Machine Removed

To configure the alert for VMware ESX Server, follow these steps:

1. select Data Manager → Alerting → Hypervisor Alerts.

2. Right-click and select Create Alert, as shown in Figure 5-59.

Figure 5-59 Creating alert for ESX VMware

3. Select the applicable triggering condition.

4. Select a triggered action to occur when the condition is met.

5. Go to the Hypervisor tab to select the ESX Server for which you want to set the Alert.


6. Press Ctrl+s to save the alert (see Figure 5-60).

Figure 5-60 Creating Hypervisor alert

Alert LogsWhenever an alert condition occurs for any of the alerts, it makes an entry to the Alert Log apart from triggering the specified action. After running the probe or scan job, you can check the Alert Log to see which conditions for which alerts have been met. As an example, we have created a Computer Alert with the Computer Unreachable condition and have run the Probe job. Some of the computers, which met the alert condition, have been detected. The following steps take you to the Alert Log:

1. Select IBM TotalStorage Productivity Center → Alerting → Alert Log.

2. Select All or Computer from the subtree.


3. The report displays if there is at least one machine that satisfies the alert condition:

a. Check the alert type to see the condition.

b. Check the alert name and alert creator to see which alerts have been satisfied.

4. In our example (Figure 5-61), the alert log shows all the computers that have met the Unreachable Condition.

Figure 5-61 Computer Alert

5. To get more information, click the magnifying glass icon (detailed information is shown in Figure 5-62).

Figure 5-62 Alert details


5.3.3 Policy ManagementWith this feature, we have another powerful capability to manage our monitored servers by applying policies, such as setting quotas, constraints, running scripts, taking automatic backups, or even extending the filesystem automatically.

The following Policy Management functions, which are shown in Figure 5-63, are available.

Figure 5-63 Policy Management node in the explorer view

As you can see, there are six areas under policy management:

� Quotas� Network Appliance Quotas� Constraints� Filesystem Extension� Scheduled Actions� Archive/Backup

In general, you can observe:

� If there is a plus sign in front, there are either more items that you can browse, or there are already user-defined entries.

� If there is no plus sign in front, there is no user-defined entry yet.

� With policy management, we have no predefined definitions of any type.


QuotasYou can set limits on the amount of storage that a user or a group of users can consume. A user can work on one computer or several computers. With TotalStorage Productivity Center for Data, you can define quotas for multiple levels:

� Network Level: Define a quota that place limits over multiple machines.

� Computer Level: Define a quota that places limits on a specific machine for a user or group of users.

� Filesystem Level: Define quotas for a user or group of users at the filesystem level.

They are available for a single User or OS User Groups.

With this capability, a user can only consume that storage that is allowed. At the same time, you can allow a user to consume more storage on one computer while limiting that user to consuming less storage on another computer. And in total, you can limit a user to consume a specified total amount of storage within the whole environment.

To create a quota, perform the following steps:

1. Select Data Manager → Policy Management → Quotas → User or OS User Group.

2. Select Network, Computer, or Filesystem from the subtree depending on which level of quota you want to control.

3. As an example, select Computer and right-click and select Create Quota.

4. The window displays the list of users. Select a user or users from the list and add that user or users to the selection window.

5. Click the Computers tab to see the list of computers or computer groups.

6. Select the computer, computers, or computer group to limit the user for the selected computers.

7. Click the Alert tab to define the quota for the user.

8. As an example, enter the value of 200 MB.

9. Schedule the job by selecting the When to Run tab.

Note: Quotas allow users to exceed the limits. Quotas just alert the system administrator or storage administrator about the quota violations. You can limit a user to use a certain amount of storage by using operating system utilities.


10.Press Ctrl+s to save the Quota job.

11.To see the result of the job, select Data Manager → Policy Management → Quotas → User → Computer → quota-name → date-time of job (Figure 5-64).

Figure 5-64 Quota for Computer job

12.To see the list of users who have violated the quotas, click IBM Total Storage Productivity Center → Alerting → Alert Log → All, as shown in Figure 5-65 on page 441.

Note: To have an up-to-date filesystem as opposed to quota information, plan to run the quota job after the scan job. The Data Manager then compares the filesystem information against the defined quotas, because the scan job collects and updates the latest status of the filesystem to Data Manager Repository.


Figure 5-65 Quota alert details

Network Appliance QuotasYou can also use the NAS support within Data Manager to work with Quotas defined using the software provided with Network Appliance (NetApp) Filers.

Using the Network Appliance node under Policy Management, you can:

� Import certain Quotas from NetApp filers when you schedule and run a Quota checking job.

� View the definition for each imported Quota.

� Determine when and how you are alerted when the hard limit defined with a NetApp Quota is close to being violated.

For example, you can define a policy to be alerted when:

� A user or user group is close to reaching the hard limit defined within the corresponding NetApp Quota.

� The space consumed on a QTree is approaching the hard limit defined within the corresponding NetApp Quota.

Specifically, the Data Manager NAS component enables you to work with the following types of Network Appliance Quotas:

� Quotas that limit the space that QTree directories can consume on a volume

� Quotas that limit the space consumed by specific users on a volume

� Quotas that limit the space consumed by specific user groups on a volume


ConstraintsConstraints are used to limit the user from putting restricted or unacceptable file types (such as MP3 files) on the monitored machine. You can define a constraint violation so precisely that you are able to detect violations committed by a certain user and regarding a certain file or file type.

The following three default constraints are available:

� TPCUser.AtRiskFile Constraint� TPCUser.ObsoleteFile Constraint� TPCUser.Orphaned File Constraint

To create the new constraint, do the following steps:

1. Select Data Manager → Policy Management → Constraints.

2. Right-click and select Create Constraint.

3. Select Filesystem or computers from the list in the Filesystem tab.


4. Click the File Types tab:

a. You can either forbid or allow certain file types.

b. You can choose predefined file types or add your own pattern, as shown in Figure 5-66.

Figure 5-66 Constraint file types


5. Click the Users tab (Figure 5-67).

You can either forbid or allow certain file types owned by selected users.

Figure 5-67 Constraint users

6. Click the Options tab (Figure 5-68). You can define an:

a. Alert on files that have not been accessed in more than a specified number of days.

b. Alert on files that are bigger than a specified number (byte, KB, MB, GB, or TB).

c. Alert on files that have set-UID root.

d. Alert on files that have not been backed up (Windows only) since they were modified in more than a specified number of days.

Figure 5-68 Constraint options


7. All of the constraints that you have selected in the previous three steps can be seen in File Filter Text in the Options window.

You can directly add new conditions or change the previously set conditions from this window. Here are examples:

a. (NAME matches any of ('*.avi', '*.jpg', 'itso*.*') AND TYPE <> DIRECTORY)

Restrict files that match a certain file pattern.

b. SIZE > 100 MB

Alerts on files whose size is greater than 100 MB.

c. ((NAME matches any of ('*.jpg', '*.mp3') AND TYPE <> DIRECTORY) OR OWNER matches any of ('guest'))

Restrict certain file types and guest user.


8. To add a new condition, perform the following steps:

a. In the Options window, click Edit Filter.

b. The Edit Filter pop-up window appears (Figure 5-69).

c. Highlight the line and right-click. The following options appear:

• New Condition• New Group• Merge• Edit• Delete• Cut• Copy• Paste

Figure 5-69 Adding a new condition

d. Click New Condition. A Create Condition pop-up window appears (see Figure 5-70 on page 447).


Figure 5-70 Condition options

e. A pop-up window is context sensitive. Depending on the selected condition, the window changes accordingly.

f. As an example, select Name, edit the Match value, and click Add.

g. As an example, select Attributes, select one of the attributes from the pull-down list (for example, Executable), and click Add.

9. Click the Alert tab to set the triggering-condition.

10.Press Ctrl+s to save the constraint.

Scheduled actionsTotalStorage Productivity Center for Data can be used to schedule any script against the monitored servers.

Tip: The Triggered action facility is used to run the scripts when certain alerts are set. However, scheduled actions can be run whenever you want without waiting for an alert condition.


Scripts work in the following way:

1. During installation, TotalStorage Productivity Center for Data creates the following directory on every server and agent machine:

– \Program Files\IBM\TPC\ca\Subagents\TPC\Data\Scripts for the Windows agent

– /opt/IBM/TPC/ca/subagents/TPC/Data/scripts for the UNIX agent

– \Program Files\IBM\TPC\Data\Scripts for the Windows server

– /opt/IBM/TPC/data/Scripts for the UNIX server

2. When the scripts run, TotalStorage Productivity Center for Data server looks in its local \scripts directory.

3. If the server finds the script, it loads it and sends it to the agent machine where you designated the script to be run.

4. The agent checks its local script directory.

5. If the agent finds a local version of the script, it ignores the script sent by the server and runs the local version.

6. If there is no script with the same name in the local agent script directory, the agent receives the script from the server, saves the script with a temporary name, and runs the script. After the script runs, the agent deletes the script.

To run the script, perform the following steps:

1. Select Data Manager → Policy Management → Scheduled Actions → Scripts.

2. Right-click and select Create Scripts.

3. Click the Computers tab. Select the computers on which you want to run the script.

4. Click the Scripts Options tab. Select the script from the drop-down list. These lists are derived from the server script directory. If you want to create a new script, then edit one and put it into the server script directory.

5. Click the When to Run tab and define the scheduled time for the script.

Important: If the script that you prepared on the server does not run, then check to:

� Make sure that no script with the same name is on the agent script directory.

� Make sure that the agent is installed by enabling the Agent may run script sent by server option.


6. Press Ctrl+s to save the script.

7. You can check the script status by selecting Data Manager → Policy Management → Scheduled Actions → Scripts → script-name → date and time.

Archive/BackupYou can integrate TPC with IBM Tivoli Storage Manager to archive or backup files. Use the Archive/Backup facility to view and edit IBM Tivoli Storage Manager archive and backup jobs that were defined to run against the files selected from the following reports:

� Reporting → Usage → Files → Largest Files

� Reporting → Usage → Files → Most Obsolete Files

� Reporting → Usage → Files → Orphan Files

� Reporting → Usage → Files → Duplicate Files

� Reporting → Backup → Most At Risk Files

� Reporting → Usage Violations → Constraint Violations

Refer to Figure 5-71, which shows the pop-up window that comes when you try to create Backup/Archive Job from this window.

Figure 5-71 Backup/Archive pop-up window

The way that an Archive or Backup job is defined differs from the other job definitions. These Archive and Backup jobs are defined on the files that you identified as a result of a certain report. Therefore, you must first define a report, which is able to determine a list of files, and then you create the Tivoli Storage Manager Backup or Archive job on that list of files. These jobs are displayed and managed from here.


For additional information about creating a Tivoli Storage Manager backup job, refer to “Tivoli Storage Manager backup and archive from Most at Risk Files” on page 404.

5.4 ReportingUse the Reporting facility of Data Manager to view both overview and detailed information about your storage. The more than 300 available reports are constructed from the statistical information collected by monitoring jobs and accumulated in the repository. The reporting features are very powerful, allowing you to select exactly the computers, storage subsystems, disks, filesystems, and even users upon which you want to report. You can view reports as tables of data or as graphical charts, which provides you with the flexibility to get a very detailed look at your information or a very high level overview.

The following major sections are available for reporting under Data Manager:

� Groups� Asset� Availability � Capacity� Usage� Usage Violations� Backup

To better demonstrate all of the reporting types, refer to Figure 5-72 on page 451. Note that not all entries are fully expanded.


Figure 5-72 The various reporting areas

Generally, remember that when using the reporting feature in Total Storage Productivity Center that all reports are to be seen as a base for your own reports. When you make any modifications, such as defining another scope, that is, you define the report to run on a single computer, the reports is going to be run in one of the following two ways:

� You run this report just one time.

� You save the report definition and the report shows up under the My Reports option in the Navigation Tree view.


5.4.1 GroupsGroups are a means to define subsequently defined reports against specific groups of computers or filesystem groups. Groups are advantageous, because they provide you with the capability of logically grouping many computers in one predefined group. As described earlier, the way to define this type of group follows the same principles, and we do not go into any more detail here.

5.4.2 AssetAsset reporting enables you to view information about the agents, clusters, computers, disks, storage subsystems, controllers, and filesystems, and general hardware inventory of storage assets within your environment. While running probes, it itemizes the information about your storage assets and provides a hierarchical view of that information so you can drill down to view your assets in greater detail. The following subcategories enable you to change your view of asset reports:

� Cluster

� Computer

� OS type

� Storage Subsystem

� System-wide

A detailed overview of these subcategories is given below.

By ClusterThis reporting category shows the assets based on Microsoft Cluster Services (MSCS) cluster membership. Clusters are subdivided into nodes and virtual servers. For each virtual server, you can see controllers, disks, filesystems, logical volumes, and exports or shares.

TotalStorage Productivity Center V3.3.2 allows you to see the asset report for HACMP on AIX. Figure 5-73 on page 453 shows an example for asset reporting for HACMP on AIX

Note: Within the Asset subtree, all of the available selections display the related information on the right side of the GUI, either in a tabbed view or in a plain view. There are no definitions, subselection, or further refining available. The basic approach is just to click to see what information displays.


To get the asset information for HACMP on AIX, select Data Manager → Reporting → Asset → By Cluster. You get a detailed description about the cluster being monitored by TPC and the respective Cluster Resource Group and the Virtual Nodes.

Figure 5-73 Asset Information for HACMP on AIX

By ComputerIn this reporting category, each computer in the environment is listed. Depending on the computer operating system type, each computer is subdivided into:

� Controllers� Disks� Volume groups� Filesystems� Exports or shares� Monitored directories

We will show you examples with AIX, Linux, or Windows computers asset reports.


To get assets for one of the machines, perform the following steps:

1. Select Data Manager → Reporting → Asset → By Computer.

2. All of the computers are listed. Select one of the computers. In our example, we selected Lead.itsosj.sanjose.ibm.com (see Figure 5-74).

Figure 5-74 Asset details for a computer

The report displays detailed information about the machine’s architecture and storage in the content pane as soon as you select the computer. Information displayed includes Hardware Details, Operating System Details, Disk Capacity Details, and so on.


To get detailed information for each component of a machine, you can select the following subtrees:

a. Controllers: This selection lists the built-in controllers of the machine. Click the controller name to get information for the controller (see Figure 5-75).

Figure 5-75 Controller’s Asset Details


b. Disks: This subtree lists the number of disks that you have attached to your computer (Figure 5-76).

Figure 5-76 List of disks

Click one of the disk definitions to get more information about the disk (Figure 5-76).


Figure 5-77 Detailed disk information

Five tabs appear:

• General: This tab displays information about the disk and allocations on the disk.

• Paths: This tab shows how the disk is seen from the operating system’s point of view.

• Latest Probe: This tab contains information gathered during the last probe, such as the physical characteristics of the disk (RPM, sector size, heads, and cylinders), defects, and errors detected.

• Probe History: This tab shows all of the probe jobs that were run for this machine since the machine’s installation.

• LUN Definition: If the CIMOM agent has been configured, the disk subsystem reports its LUN configuration.


c. Volume Groups: This subtree lists Volume Groups (for UNIX only). Click the Volume Group to display details. You can get additional information about the disks that construct the Volume Group and the filesystem on the Volume Group (Figure 5-78).

Figure 5-78 Detailed Volume groups

d. Filesystems or Logical Volumes: This subtree lists the filesystems and logical volumes on the selected computer, as shown in Figure 5-79 on page 459.

Two tabs are available:

• Filesystems: This tab shows you the information about the filesystem, such as capacity and number of inodes, and the scan jobs and probe jobs that are run for the selected computer.


Figure 5-79 File System details

• Logical Volumes: This tab shows us the volume, which constructs the filesystem, as shown in Figure 5-80.

Figure 5-80 Logical Volume details


e. Exports or Shares: This subtree lists the directories that are shared, as shown in Figure 5-81.

Figure 5-81 Export information


f. Monitored Directories: To view a report on a directory that you are monitoring, expand the Monitored Directories node on the Navigation Tree and click the directory for which you want to see details (Figure 5-82).

Figure 5-82 Monitored Directories information


By Hypervisor In the latest version of TPC, the asset report for VMware ESX Servers is enabled. This selection lists the configured VMware ESX Servers and their respective Virtual Machines, as shown in Figure 5-83. We cover the VMware ESX Server reports in 5.8, “VMware ESX Server support” on page 529.

Figure 5-83 Asset Report for ESXVMware Server

By OS Type Computers are grouped into operating system type. The following operating system types are available:

� Windows NT®� Windows� Microsoft Cluster Resource Group� Solaris� Linux� Hewlett-Packard UNIX (HP-UX)� AIX� HACMP Cluster Resource Group� NetWare� Network Appliance� Other NAS


� IBM storage area network (SAN) FileSystem� VMware ESX

To get the assets for one of the Windows machines, do these steps:

1. Select Data Manager → Reporting → Assets → By OS Type.

2. The list of OS types displays. We selected Windows in order to view the list of Windows machines in the environment, as shown in Figure 5-84. You can drill down to see additional information, such as Controllers, Disks, Filesystems, Exports or Shares, and Monitored Directories.

Figure 5-84 OS report


3. Click one of the machines to get information about the computer that has a Windows operating system running, as shown in Figure 5-85. You can drill down to the sub menus to see the detailed information about Controllers, Disks, Filesystem or Logical Volumes, Exported directories, and Monitored directories.

Figure 5-85 Details of a Windows Machine

By Storage SubsystemThis selection lists the available storage subsystems in the environment. For example, you can view the following information (Figure 5-86 on page 465):

� For an ESS subsystem, you can view disk groups, volume spaces, disks, and LUNs.

� For DS6000 and DS8000, you can view Disks, ArraySite, Ranks, Extendpools, and Volumes

� For a SAN Volume Controller (SVC), you can view managed disk groups, managed disks, and virtual disks.


� For IBM FAStT and HP StorageWorks, you can see storage pools, disks, and LUNs.

� For Hitachi Data Systems, you can see storage pools and LUNs.

Figure 5-86 Asset by Storage Subsystems

With IBM TotalStorage Productivity Center V3.3.2, we can see the Space-Efficient Volumes reports for DS8000, but we cannot use Disk Manager to create or delete Space-efficient Volumes.


To see the reports for Space-efficient volumes, select Data Manager → Reporting → Assets → By Storage Subsystem and select the Space-efficient volume under the DS8000 storage subsystem. This will show you the details of the Space-efficient Volume in the content pane (Figure 5-87).

Figure 5-87 Report for Space-efficient volume

System-wideThis selection allows you to view the assets on the entire environment. The data is aggregated and shown as a system-wide report. For example, the following subtrees are available, as shown in Figure 5-88 on page 467.


Figure 5-88 Asset System-wide subnodes

Agents The System-wide → Agents report enables you to track and monitor the Data agents deployed in your storage environment. This report enables you to:

� View information about the agents deployed in your environment.

� Perform actions against one or more agents shown in the report.

To get the report for agents, use the following steps:

1. Select Data Manager → Reporting → Assets → System-wide → Agents. The Report Generation window appears.


2. Select the columns that you want included and excluded and click Generate Reports. TotalStorage Productivity Center for Data lists all of the agents that are registered in addition to information about the agents, such as Agent Status, OS Type, Version, Host ID, Host Address, Last Update, Time Zone, Connection Errors, Consecutive Errors, and CPU Architecture (Figure 5-89).

Figure 5-89 Agent reports

You can click the Magnifying glass icon next to each agent to get more detailed information.

ComputersTo create the report for computers, follow these steps:

1. Select Data Manager → Reporting → Assets → System-wide → Computers. The Report Generation window appears.

2. Select the columns that you want included and excluded and click Generate Report. TotalStorage Productivity Center for Data shows you all of the computers, as shown in Figure 5-90.

Figure 5-90 Computer Asset Reports


3. Clicking the magnifying glass icon shows you a detailed report for the computer in addition to the following information:

– Network Address– IP Address– OS Type– OS Version– Time Zone– Manufacturer– Model– Serial Number– Processor Type– Processor Speed– Processor Count– RAM– Swap Space– Disk Capacity– Unallocated Disk Space– Filesystem Free space– Last Boot Time– Last Probe Time– Last Probe Status– Discovered Time– CPU Architecture

DisksTo get the report for disks, follow these steps:

1. Select Data Manager → Reporting → Assets → System-wide → Disks. The Report Generation window appears.

2. Select the columns that you want included and excluded and click Generate Report.


3. TotalStorage Productivity Center for Data lists all of the disks with additional information about the disks, such as Path, Manufacturer, Model, Storage System, RPM, Capacity, and Number of Defects (Figure 5-91).

Figure 5-91 Disk reports

In addition to the above reports, we can also see some other reports in the System wide reports. We can generate them in the same way as the above reports. Here is the list of those reports:

� Storage Subsystems Reports

� Unmanaged Virtual Machine Reports

� Virtual Machines with no VMware Agent installed

� FileSystem or Logical Volumes Reports

� LUNs Reports

� Exports and Shares Reports


� Monitored Directories Reports

� Unmanaged Computers Reports

� Users Reports

5.4.3 AvailabilityTotalStorage Productivity Center for Data can keep track of all agents’ availability for the agents that are registered on it. Uptime and statistics regarding sending and receiving signals are saved and can be seen as a report. Two subcategories are available: Ping and Computer Uptime.

To get a ping statistic for one of the machines, follow these steps:

1. Select Data Manager Reporting → Availability → Ping.

2. Five subcategories can be selected:

a. By Clusterb. By Computerc. By Computer Groupd. By Domaine. Network-wide

3. For example, click By Computer. The Selection window appears, as shown in Figure 5-92. We can limit the report for a certain date range or certain computers. If nothing is selected, the report works for all date ranges and for all of the computers in the environment.

4. Click Generate Report.

Figure 5-92 Ping by computer

To get a Computer Uptime report for one of the machines:

1. Select Data Manager Reporting → Availability → Computer Uptime.


2. Five subcategories can be selected:

a. By Clusterb. By Computerc. By Computer Groupd. By Domaine. Network-wide

3. For example, click By Computer. See Figure 5-93. Ping by cluster can be used to ping Microsoft Cluster and HACMP on AIX.

4. Click Generate Report.

5. The report displays the availability of the computer and how many times it has been booted.

Figure 5-93 Computer Uptime report

5.4.4 CapacityCapacity information is also available in the repository. TotalStorage Productivity Center for Data can report this value again by several options, such as by disk, by storage subsystem, by cluster, by computer, by computer group, by domain, and network-wide.

Four subcategories are available:

� Disk Capacity� Filesystem Capacity� Filesystem Used space� Filesystem Free space

For example, to get the disk capacity for a network-wide view, follow these steps:

1. Select Data Manager → Reporting → Capacity → Disk Capacity.

2. Click Network-wide and the Report generation window appears.

3. Click Generate Report to create the report for Network-wide.


4. One line displays for Network-wide. Click the Pie chart icon to view the report in chart format, as shown in Figure 5-94.

Figure 5-94 Disk capacity reports

5. To focus on the disk capacity for each computer, click the Network-wide tab and click the magnifying glass located to the left of the line. The Disk Capacity report for all of the computers displays, as shown in Figure 5-95.

Figure 5-95 Disk Capacity by Computer report


6. To get details for an individual row, click the magnifying glass icon to the left of the row, as shown in Figure 5-96.

Figure 5-96 Disk Capacity By Disk report

7. Note that you can get more details about the disk on the selected computer by accessing the TotalStorage Productivity Center for Data report, which you can do by selecting Data Manager → Reporting → Asset → By Computer → computer name → Disks.

8. Right-click and select Chart: All rows, as shown in Figure 5-97.

Figure 5-97 Chart Disk Capacity

The line graph to chart all of the disk capacity by computer is shown in Figure 5-98 on page 475.


Figure 5-98 Disk Capacity by Computer

To get network-wide filesystem capacity, follow these steps:

1. Select Data Manager → Reporting → Capacity → Filesystem Capacity.

2. Click Network-wide. The Report Generation window appears.

3. Click Generate Report to create the report for network-wide.

4. One line displays for network-wide.

The report shows the following information:

– Capacity– Percent Used Space– Used Space– Free Space– Filecount– Directory Count– Percent Used Inodes– Free Inodes

5. Click the magnifying glass icon to see all of the computers in the environment.


6. Right-click and select Chart space usage for all.

7. You get a report of Used Space and Free Space of two computers at a time.

8. Right-click and select Customize this chart to change the chart type or the number of computers shown at a time, as shown in Figure 5-99.

Figure 5-99 Filesystem capacity report

A history report can be important for you to predict the future of your capacity depending on current trends. To get a history report:

1. Select Data Manager → Reporting → Capacity → Filesystem Used Space.

2. Click By Computer. The Report generation window appears.

3. Click the magnifying glass icon next to one of the computers.

4. Right-click and select History Chart: Used Space for selected.

The chart shown in Figure 5-100 on page 477 displays, starting from the first scan to the last scan.


Figure 5-100 History Chart: Space Used

5.4.5 UsageUsage reporting enables you to report on the usage and growth of the consumption of your storage. TotalStorage Productivity Center for Data can report this value again through several options, such as by disk, by storage subsystem, by cluster, by computer, by computer group, by domain, and network-wide.


Here are the categories that are available under Usage Reports. Figure 5-101 shows the navigation path under the Usage Reports.

� Access Load� Files� Directories� Users� OS User Groups

Figure 5-101 The major categories in Usage reporting

We have already seen several reports in 5.2.1, “Predefined reports under the My Reports node” on page 392. In this section, we show several reports that were not mentioned in the My Reports section.

To get a Creation Time report, do these steps:

1. Select Data Manager → Reporting → Usage → Access Load → Creation Time.

2. Click Network-wide.

3. The Report generation window appears. Select the profile.


5. One line of the report tells us the number of files that were created in:

– Less than 1 day – Within 1 week– Within 1 month


– Between 1 and 2 months– Within 1 year– More than 1 year

6. Click the pie chart icon to view the report in pie chart format, as shown in Figure 5-102.

Figure 5-102 Creation Time report in pie chart format

You can view the usage reports for files also, which gives you the details for the number of files and their occupied space on the basis of file type. To get a File Types report, do these steps:

1. Select Data Manager → Reporting → Usage → Files → File Types.

2. Click Group by File Type and Network-wide.



5. This lists all of the file types within all computers.

6. To select specific file types, click Selection.


7. File types appear in a pop-up window. Put a check mark on the file types that you want to include in the report (for example, check only the following file types: avi, bmp, db2, db, jpg, and zip.)

8. The report shows the number of files, Type Description, Total Size of the file, and percentage of used space (Figure 5-103).

Figure 5-103 File type network-wide

9. Click the magnifying glass icon to the left of the line in Figure 5-103 to display the computers that have the selected file types, for example, computers that have *.jpg files (Figure 5-104).

Figure 5-104 Detailed file type by computer

To get a Duplicate File report:

1. Select Data Manager → Reporting → Usage → Files → Duplicate Files.

2. Click By computer. The Report generation window appears.

3. To select the computer, click Selection. Select only one computer.


4. This report lists duplicate files for the selected computer (Figure 5-105).

Figure 5-105 Duplicate file report


5. Click the magnifying glass icon in Figure 5-105 on page 481 to get details about a selected file (Figure 5-106).

Figure 5-106 Duplicate File Details

6. You can automatically trigger a Tivoli Storage Manager backup and then delete the file if you want. To trigger a backup this way in the duplicate file list window, highlight the file, right-click, and select Create a new archive/backup job.

5.4.6 Usage violationsWhen you set up quotas or constraints in Policy Management, TotalStorage Productivity Center for Data starts to check the usage against the quotas and the constraints.

You have seen several of these reports already in 5.2.1, “Predefined reports under the My Reports node” on page 392.

5.4.7 BackupBackup reporting allows us to see the files that are most at risk and the files that have been modified but not backed up. At this list, we can run backup jobs against the files, and, therefore, we can be proactive about saving the files.


This node of the explorer view has the following subnodes:

� Most at Risk Files� Modified Files not Backed Up� Backup Storage Requirements

Use the following steps to get the report for the Most at Risk Files:

1. Select Data Manager → Reporting → Backup → Most At Risk Files.




5. The file list displays. It is sorted by Modification Time, as shown in Figure 5-107.

Figure 5-107 Most At Risk Files

6. Select a file or files from the list, right-click, and select Create a new archive/backup or Add an existing archive/backup job.


7. The Create File Archive/Backup Action window appears. Select the backup type, such as Archive, Selective backup, or Incremental backup (Figure 5-109 on page 485).

Figure 5-108 Backup options

8. Click the When to Run tab to schedule the backup job.

9. Press Ctrl+s to save the job. You can follow the status of the job by selecting Data Manager → Policy Management → Archive/Backup → job-name → date-time.

If you decide to back up or archive the files to Tivoli Storage Manager, you might need to know how much storage is needed by the Tivoli Storage Manager server to back up the selected files. By having this information, you can calculate the time needed to back up the files or calculate the disk or tape storage needed for the files. TotalStorage Productivity Center for Data can also give you this information.

Backup Storage requirement is an excellent tool for planing the storage pool or tape requirement for your backup environment. It has the ability to generate multiple reports, such as Full backup and Incremental.

These reports can be generated by Directory, by Directory Group, by Filesystem, by Filesystem Group, by Cluster, by Computer, by Computer Group, by Domain and Network Wide. These reports allow you to see, for any of these levels, how much data would need to be backed up for any of these desired time intervals. This is useful for determining backup sizing and can be used to determine appropriate backup groups and setting the timing of your backups.

To obtain the total size of the backup, follow these steps:

1. Select Data Manager → Reporting → Backup → Backup Storage Requirements → Full Backup Size.





5. One line of the report tells us the total backup size (Total Size) and the total number of files to back up (File Count), as shown in Figure 5-109.

Figure 5-109 Backup requirements

6. You can click the magnifying glass icon to display a report for each computer, as shown in Figure 5-110.

Figure 5-110 Detailed backup storage requirements


7. You can click the magnifying glass icon again to get the filesystem list for each computer, as shown in Figure 5-111.

Figure 5-111 Detailed backup storage requirements by filesystem

5.5 Reporting for databasesThis section describes the TotalStorage Productivity Center Data Manager for Databases, which is similar to the TotalStorage Productivity Center Data Manager in that the reporting uses the data in the repository and the reports can be displayed as either tables or as graphical charts.

Data Manager for Databases can be integrated into Oracle, Microsoft SQL/Server, Sybase, and IBM DB2 Universal Database, and can extract details about database and tablespace usage. You can also enable monitoring for predefined events to occur and alert you to potential situations before they occur.

For example, it can notify you when an Oracle table space is reaching a critical shortage of free space or when a Sybase table is dropped. By alerting you to these and other issues related to your stored data for the databases within your environment, it enables you to prevent unnecessary system and application downtime.

In this section, we show you how to register a database and extract capacity and usage reports.

To better demonstrate all of the reporting types, refer to Figure 5-112 on page 487. Note that not all entries are fully expanded.


Figure 5-112 Data Manager for Databases reporting areas


5.5.1 Register the databaseBefore we can create probes and scans and then extract data from our databases, we need to first register the database to TotalStorage Productivity Center for Data. In these steps, we register our database instance, which is installed on one of our hosts, to TotalStorage Productivity Center for Data:

1. Select Administrative Services → Configurations → License Keys, as shown in Figure 5-113.

Figure 5-113 Register the database

2. In Figure 5-113, select the magnifying glass icon that is located to the left of the line TPC for Data - Databases. Figure 5-114 appears.

Figure 5-114 License Keys detail


3. In Figure 5-114 on page 488, select the RDBMS Logins tab, and then select Add New. Configure the login properties for your database instance on the target server, as shown in Figure 5-115.

Figure 5-115 RDBMS Login Editor window

4. After you click Save in Figure 5-115 to complete this task, you get a success message, as shown in Figure 5-116. You will now see that the new database host and information are listed after the configuration.

Figure 5-116 RDBMS success message


5.5.2 Set up probes and scansAfter we have registered the database, we need to create a probe to extract information from the database:

1. Select Data Manager for Databases → Monitoring → Probes. Right-click and select Create Probe, as shown in Figure 5-117.

Figure 5-117 Creating a probe


2. You can add Instances and use the arrows to move the instances to the Current Selections column. In Figure 5-118, select File → Save and give the probe a name. Select OK, and the probe will be submitted.

Figure 5-118 Configure and save the probe


3. Monitor the job until it completes (Figure 5-119).

Figure 5-119 View the probe job’s success


4. Next, we need to create a scan to gather more detailed information about the database. Select Data Manager for Databases → Monitoring → Scans. Select the default scan and select Run Now, as shown in Figure 5-120.

Figure 5-120 Running a scan


5. Monitor the scan job until it completes (Figure 5-122 on page 495).

Figure 5-121 Monitor the scan

5.5.3 Database capacity reportsCapacity information for databases is available in the repository. TotalStorage Productivity Center for Data can report several types of detailed information categorized by database, instance, computer, computer group, and network-wide.

For example, to get the Total Instance Storage Capacity for a view by computer, follow these steps:

1. Select Data Manager for Databases → Reporting → Capacity → All DBMSs → Total Instance Storage.

2. Click By Computer and the Report generation window appears.


3. Click Generate Report to create the report By Computer. The report displays the capacity for each computer (Figure 5-122).

Figure 5-122 Total Instance Storage by Computer


4. Click the magnifying glass icon to view a selected server, as shown in Figure 5-123.

Figure 5-123 Total Instance Storage by Computer

5. Now, drill down on the selected computer for instance information (Figure 5-124).

Figure 5-124 Instance Information on selected computer

6. If you click the magnifying glass icon, you can get a listing of the Database Files, as shown in Figure 5-126 on page 498.


Figure 5-125 Listing of all database files

5.5.4 Database usage reportsDatabase usage reporting information is available in the repository. TotalStorage Productivity Center for Data can report on this data in several ways, such as By Database, By Instance, By Computer, By Computer Group, and Network-wide.

For example, to get the Total Instance Storage Capacity view By Computer, follow these steps:

1. Select Data Manager for Databases → Reporting → Usage → All DBMSs → Databases-Tablespaces.

2. Click Enterprise-wide and the Report generation window appears.


3. Click Generate Report to create the report (Figure 5-126).

Figure 5-126 Creating a Database Usage report


4. The report displays a Network-wide Summary report (Figure 5-127).

Figure 5-127 Network-wide Summary report


5. Now, click the line graph icon, and you see the Usage graph report (Figure 5-128).

Figure 5-128 Database usage graph

5.6 TopologyThe Topology Viewer provides a graphical representation of the physical and logical resources (for example, computers, fabrics, storage subsystem, and so on) that have been discovered in your storage environment by TotalStorage Productivity Center. In addition, the Topology Viewer depicts the relationships among resources (for example, the disks comprising a particular storage subsystem). Detailed tabular information (for example, attributes of a disk) is also provided. With all the information that the Topology Viewer provides, you can more quickly and easily monitor and troubleshoot your storage environment and perform critical storage-management tasks.

The overall goal of the Topology Viewer is to provide a central location to view a storage environment, quickly monitor and troubleshoot problems, and gain access to additional tasks and functions within the TotalStorage Productivity Center graphical user interface (GUI) without users losing their orientation to the environment. This kind of flexibility through the Topology Viewer UI displays better cognitive mapping between the entities within the environment, and


provides data about entities and access to additional tasks and functionality associated with the current environmental view and the user's role.

The Topology Viewer uses the TotalStorage Productivity Center database as the central repository for all data it displays. It actually reads the data in user-defined intervals from the database and, if necessary, updates the displayed information automatically.

The Topology Viewer was introduced in TotalStorage Productivity Center Version 3.1 and has been significantly enhanced in Version 3.3 and later.

To launch the topology viewer, select IBM TotalStorage Productivity Center → Topology (Figure 5-129). This will show you a high level view of all the components in your environment (Figure 5-129). By clicking an individual component, you can see more details for that component.

Figure 5-129 Topology Viewer overview


The new features that were introduced in TotalStorage Productivity Center for Data for the Topology Viewer are:

� Pin list persistence� Topology Viewer link to reports and alerts � Context Sensitive Reporting and Data Path Explorer Capacity� GUI navigation tree enhancements

5.6.1 Pin list persistence

The pin list feature in the Topology Viewer in TotalStorage Productivity Center allows the you to “pin” an entity, which puts a small flag next to the entity and propagates this flag to all views that contain that entity. This feature is useful for marking entities for various reasons, such as a reminder to look at this entity later and for upward propagation. Pinned entities are typically of great interest to the user for monitoring purposes, and easy access to these entities is essential. Through pinning, the Topology Viewer can provide functionality that is similar to NetView SmartSets.

Pin lists for multiple users and multiple user namesMultiple users, that is, people using various user names to log into TotalStorage Productivity Center, now can have their own persistent and private pin lists. When multiple users log on to the same TotalStorage Productivity Center server simultaneously using the same user name, they will share the same pin list.

The pins will remain visible until you unpin them in the Topology Viewer. This enables a user to easily refer to a small number of entities when using the TotalStorage Productivity Center GUI.

Use the following steps to pin a computer entity:

1. Select IBM TotalStorage Productivity Center → Topology and open the Background Context Menu by selecting an entity.

2. Right-click and select Pin (Figure 5-130 on page 503).

Note: In TotalStorage Productivity Center V3.1, the pin list in the Topology Viewer is not persistent across sessions. If the user closes the TotalStorage Productivity Center GUI (or even just the Topology Viewer window), the user loses the current pin list. Now with TotalStorage Productivity Center V3.3 and later, the pin list is stored in the database and is persistent across sessions and for each user.


Figure 5-130 Pinning an entity

3. Figure 5-131 on page 504 shows the entities that we have pinned in the Topology Viewer Overview window.


In general, note that pinning provides a direct path to look at an entity in detail just by double-clicking it. Notice that in a collapsed group, the pinned entities are displayed (Figure 5-131). In an expanded group, pinning is shown on each pinned entity.

Figure 5-131 Pinned entities surfaced in a group

5.6.2 Link to reports/alerts from the Topology Viewer

With TotalStorage Productivity Center V3.3 and later, the reports and alerts are integrated into the GUI console. This feature provides a mechanism to navigate from an entity shown on the Topology Viewer to other areas of the console to show alerts or reports or to manage the selected entity. This enhancement enables users to directly launch to the appropriate portions of the console Navigation Tree from the Topology Viewer.


Link to alertsFrom the Topology Viewer, you might notice that there is a red exclamation point character (!) shown beside an entity or in the group title, which indicates that there are alerts for this entity or entities within the same group. You can hover your mouse over the red exclamation point, and it shows you the number of alerts that are now open for the selected entities (Figure 5-132).

Figure 5-132 Topology Viewer alert summary


Use the following steps to launch alerts from the Topology Viewer:

1. Right-click the entity and choose Show <entity type> Alerts (in our example, we are looking at the Switches Group, so the option is Show Computer Alerts), as shown in Figure 5-133.

Figure 5-133 Topology Viewer Show Computer Alerts

2. The TotalStorage Productivity Center for Data GUI then launches the related alert view, as shown in Figure 5-134 on page 507. You can look at the alert and then choose Clear to acknowledge the alert or Delete to delete the alert if you do not need the information any longer.


Figure 5-134 Alert details

Link to reportsIn the Topology View, from the L0-L2 graphic view of Computers and Storage classes, you can link to reports that reflect the entities from which you choose. This function is extremely convenient when you look at an entity or a certain group of entities, and you want to view a report to see more information.


Here is a example of creating a report from the Computer group graphic view:

1. Select the title of the Computer group, right-click, and select Reports from the pop-up context menu, as shown in Figure 5-135.

Figure 5-135 Topology Viewer Report navigation

Note: Do not right-click the computer entity, because then the report information will only reflect that computer.


2. The pop-up window displayed shows the available reports (related to the selected entity) that you can generate. In our example, we select Data Manager → Capacity → Filesystem Used Space → By Computer, and click Create Report (see Figure 5-136).

Figure 5-136 Entity report selection


3. TotalStorage Productivity Center GUI then brings up the TotalStorage Productivity Center Generate Report window (Figure 5-137).

Figure 5-137 Report navigation to Generate Report for selected group entity

4. Select the columns that you want included or excluded and click Generate Report. TotalStorage Productivity Center displays a Filesystem Used Space report for the selected computer group in the selected Topology Viewer, as shown in Figure 5-138 on page 511.


Figure 5-138 Report from selected entity group in Topology Viewer

5.6.3 Context Sensitive Reporting and Data Path Explorer

A new view has been added to the Topology Viewer that allows the user to view the paths between servers and storage subsystems or between two storage subsystems (for example, SVC to back-end storage or two subsystems participating in a replication session). Performance and health overlays on this view provide a mechanism to assess the impact of performance in the paths connecting the systems and the device states. The view consists of three panes (host information, fabric information, and subsystem information) that show the path through a fabric or set of fabrics for the endpoint devices (host to subsystem or subsystem to subsystem).

The goal of this improvement is to identify the impact of performance issues in a fabric or the devices that are connected to the fabric on the other components in the environment. To identify the impact of performance issues, define the performance monitor for related subsystems and switches.

Data Path Explorer prerequisitesYou need to have the following TotalStorage Productivity Center agents in order to view the data paths from a host to a subsystem:

� You must have a CIM agent for the subsystem.

� You need a Data agent on the host.


� You must have an in-band or out-of-band Fabric agent.

� Note that in an “out-of-band Fabric agents only” environment, the out-of-band agents need to be configured for all of the switches in a fabric.

� A CIM Agent for the SVC is needed to view data paths involving the SVC.

� No data paths show if any one of the previous agents is not configured.

� For a zone overlay with SMI-S compatible SAN switches, you do not need CIMOMs. You need an in-band Fabric agent for non-SMI-S compatible SAN switches.

� For a performance overlay, you need to configure switch and subsystem performance monitors.

� Only the subsystem device driver (SDD) is supported for Multi-path driver on all OS platforms. On Windows, SDD V1.6.1 or greater is needed.

To launch the Data Path Explorer, in Topology Viewer, select one or more hosts, subsystems, disks, volumes, or Mdisks and click the Data Path Explorer shortcut in the MiniMap tool (see Figure 5-139).

Figure 5-139 MiniMap with Data Path Explorer shortcut

Note: In order to view the Data Path Explorer for a host, you must have the Data agent and an out-of-band Fabric agent on the SAN or SIM-S configured on the SAN Switch to which the host is connected.


The Data Path Explorer view for hosts is shown in Figure 5-140. From this view, you can see how the host volumes connect through the fabric to the storage subsystem.

Figure 5-140 Data Path Explorer view for hosts


The Data Path Explorer view for a subsystem is shown in Figure 5-141. If the subsystem is an SVC, you can see from this view how the SVC MDisks connect through the fabric to the SVC’s back-end storage subsystem. If the subsystem is not an SVC, you can see from this view how the subsystem connects to its hosts.

Figure 5-141 Data Path Explorer view for a subsystem

The Data Path Explorer view for an MDisk is shown in Figure 5-142 on page 515. From this view, you can see how the MDisk comes from its back-end subsystem.


Figure 5-142 Data Path Explorer view for Mdisk

The Data Path Explorer view for a volume is shown in Figure 5-143. From this view, you can see how the volume from the subsystem connects to an SVC or hosts.

Figure 5-143 Data Path Explorer view for volume


5.7 Enterprise Server Rollup functionTotalStorage Productivity Center now enables you to use a single interface to generate reports based on data collected by multiple TotalStorage Productivity Center servers. This feature is known as Enterprise Server Rollup feature. With this feature, you will be able to perform the following:

� View the storage information that is gathered by other servers from a single TotalStorage Productivity Center user interface using new enterprise-wide rollup reports. These rollup reports enable you to have a network-wide perspective of storage usage in an environment where multiple TotalStorage Productivity Center servers are deployed and collecting storage metrics.

� Partition a large number of agents across multiple Data servers. This will alleviate performance issues when running aggregation reports and scan jobs for multiple agents on one Data server.

To enable rollup reporting, you must select one TotalStorage Productivity Center server to act as the “master” server that gathers enterprise-wide data for reports. You can then associate other IBM TotalStorage Productivity Center servers to that master server as “subordinate” servers. These subordinate servers provide data to the master server about the entities they manage.

5.7.1 Rollup Reporting recommendationsKeep in mind the following information when working with master and subordinate servers:

� The master and subordinate servers can change over time.

� A master server can also manage entities just like any other server and report on these entities.

� The Enterprise Server Rollup function requires that TotalStorage Productivity Center Standard Edition is installed on the master server. If the Standard Edition is not installed, the necessary nodes for configuring the subordinate TotalStorage Productivity Center servers and Rollup Reports are not available.

� TotalStorage Productivity Center servers must be at Version 3.3 or greater to use this feature. Both the master and the subordinate servers must be at Version 3.3 or greater.

� We recommend that the master server should monitor no more than 500 unique data sources. This number includes subordinate servers, Data agents,

Note: Performance-related data, and therefore reports, are not rolled up.


Fabric agents (Inband and Out of Band), CIMOM agents, and VM servers (VMware).

� We recommend that each subordinate server monitors no more than 1200 unique data sources. This number includes Data agents, Fabric agents (Inband and Out of Band), CIMOM agents, and VM servers (VMware). Once this threshold has been met for a server, a new server should be deployed and all new agents pointed to it.

� You must have TotalStorage Productivity Center superuser or IBM TotalStorage Productivity Center administrator authority to perform administrative operations such as adding a subordinate server to the master server list to monitor.

� After upgrading to TotalStorage Productivity Center V3.3 or later from a previous version of the application, you must run probes against a master server's monitored storage assets to have information about those assets appear in the Navigation Tree IBM TotalStorage Productivity Center → Rollup Reports path.

� When you add a subordinate server to the master server list, you must provide the host authentication password of the subordinate server to the master server. The host authentication password is checked each time the master server is probed. This host authentication password is entered when installing TotalStorage Productivity Center.

Rolled up data from TotalStorage Productivity Center subordinate servers is stored in new tables in the master TotalStorage Productivity Center server. Otherwise, all of the existing TotalStorage Productivity Center reports need to be modified if rollup data is put into the existing T_RES_*** tables. Using TotalStorage Productivity Center V3.3 with new table definitions allows you to create, store, and retrieve rolled up data.


Figure 5-144 shows an overview of the TPC Enterprise Rollup Feature.

Figure 5-144 TPC Enterprise Rollup feature overview

In this section, we describe:

� How to define subordinate TotalStorage Productivity Center servers to the master TotalStorage Productivity Center server.

� How to combine reports for multiple TotalStorage Productivity Center servers into an enterprise-wide Rollup Report, which gives the client a complete view of its environment.

5.7.2 Creating Rollup reportsThe following subsections describe the definition, execution, and report generation process of the TotalStorage Productivity Center Rollup feature. The first step is to identify the server that will be the master. Launch the TotalStorage Productivity Center server GUI and log in to the TotalStorage Productivity Center GUI as a TotalStorage Productivity Center superuser or administrator. Perform


the following steps on the master TotalStorage Productivity Center server to add a subordinate TotalStorage Productivity Center server:

1. Expand Administrative Services → Data Sources in the Navigation Tree.

2. Click TPC Servers.

3. Click Add TPC Server.

Figure 5-145 shows the result of performing these steps.

Figure 5-145 TotalStorage Productivity Center subordinate server definition

After the Add TPC Server window appears, enter:

� A host name or IP address of the TPC server. We recommend that you enter a Fully Qualified DNS Name.

� A host Device server port. The default port is 9550.

� The host authentication password (which is the TotalStorage Productivity Center host authentication password of the Device server).

� Optionally, enter a display name.


� Optionally, enter a description

� Select Test TPC Server connectivity before adding in the Add TPC Server window for a subordinate TotalStorage Productivity Center server that is up and running and whose authentication data matches the data of the data provided in the Add TPC Server window.

� Click Save on the Add TPC Server window.

Adding a subordinate serverThe TotalStorage Productivity Center GUI sends the request to the TotalStorage Productivity Center master server to add the TotalStorage Productivity Center subordinate server and perform a check. The TotalStorage Productivity Center master server verifies that the subordinate TotalStorage Productivity Center server is not already being monitored. The TotalStorage Productivity Center master server will verify that the login information for the subordinate TotalStorage Productivity Center server is correct by connecting to the remote TotalStorage Productivity Center subordinate server. After these verification steps are completed, the TotalStorage Productivity Center master server adds the subordinate TotalStorage Productivity Center server to its database and returns a success code to the TotalStorage Productivity Center GUI. The window shown in Figure 5-146 on page 521 illustrates the successful addition of a TotalStorage Productivity Center subordinate server.


Figure 5-146 Successfully adding a TotalStorage Productivity Center subordinate server

5.7.3 TotalStorage Productivity Center server probe process

The information from TPC subordinate servers is extracted by using the TPC Device server Probe. Probing is the process of gathering detailed information from within the TPC subordinate server, such as storage subsystems usage statistics and asset information about computers, clusters, and fabrics.

When a probe is run, the Data server on the master TPC server authenticates with the Device servers on the subordinate TPC servers by using host authentication passwords that are provided when the subordinate TPC servers are defined. The Data server on the master TPC server then makes Web service calls to the TPC Device server on the subordinate TPC server. Batch reports can be generated for any TPC Data agent that is being directly monitored by the TPC master server from which the enterprise-wide rollup reports are generated.


To probe subordinate TPC servers, you must create a probe definition. By default, all of the newly registered subordinate servers are added in the default TPC server probe definition. Prior to scheduling a TPC Server probe, verify that at least one subordinate TPC server with data is being monitored by the master TPC server.

To schedule a TPC server probe, perform the following steps from the master TPC server:

1. From the main Navigation Tree pane, select IBM TotalStorage Productivity Center → Monitoring → TPC Server Probes.

2. Under the What to Probe tab, select All TPC Servers, which is depicted in Figure 5-147, and all of the resources will be probed.

3. You also can select a specific TPC server to probe, as well as the class of information to pull from the probed servers (subsystem, fabric, computers, clusters, tapes, or databases). This information is stored in the master server’s local database.

Figure 5-147 Probe of TPC servers for Rollup Reports

The results of a successful TPC subordinate probe are shown in Figure 5-148 on page 523, depending the number of TPC subordinate servers selected and the data gathered.


Figure 5-148 Subordinate server probe results

5.7.4 Generating TotalStorage Productivity Center V3.3 Rollup Reports

IBM TotalStorage Productivity Center includes multiple Rollup Reporting categories that provide you with the flexibility to view data about your storage resources according to the needs of your environment. The following Rollup Reporting categories are available:

� Asset: These reports provide detailed statistics about agents (TPC), computers, storage subsystems, disk and volume groups, disks, filesystems, logical volumes, LUNs, and fabrics.

� Database Asset: These reports provide detailed statistics about the RDBMSs in your environment, including Oracle, SQL Server, Sybase, and DB2 UDB.

� Capacity: These reports provide storage metrics related to the disk capacity, the filesystem capacity, the filesystem used space, and the filesystem free space of the storage entities in your environment.


� Database Capacity: These reports provide storage metrics related to the storage capacity of the RDBMS in your environment, including Oracle, SQL Server, Sybase, and DB2 UDB.

How to generate Rollup Reports To generate an enterprise Rollup Report, expand the Navigation Tree to display the type of report that you want to generate. For example, if you want to generate a Disk Capacity report, expand Data Manager → Rollup Reports → Capacity → Disk Capacity.

To view the Rollup capacity information according to a storage subsystem, select Rollup Reports → Capacity → Disk Capacity → By Storage System. Figure 5-149 shows the Selection page. Use the Available Columns and Included Columns list boxes to determine what columns to display in a generated report.

Figure 5-149 Storage Subsystem Capacity Rollup Report


Use the Selection window to select the profile to use when generating a report and determine which columns appear within the report. Click Selection to select the objects on which you want to report from the Select Resources window (Figure 5-150). Click OK.

Figure 5-150 Storage Subsystem Selection for Rollup Reports


Click Filter to further filter the objects that appear in a report. Filters enable you to apply general rules to the report based on the rows in that report. Figure 5-151 illustrates the Filter window.

Figure 5-151 Filter for Rollup Reports

Click Generate Report. A new tab will be added to the tab window representing the report that you generated. Reports are tabular in format and are comprised of rows and columns. You can scroll the report up and down and to the right and left to view the entire report. Use the View menu to hide or show the Navigation Tree to increase the viewable area of the report or drag the divider bar in the middle of the window back and forth to reallocate the amount of space that is given each pane. Figure 5-152 on page 527 is an example of a Storage Subsystem Capacity Rollup Report.


Figure 5-152 Storage Subsystem Capacity Rollup Report

Asset Information Report by computerThe next example guides you through the generation of an Asset Information Report by computer. To generate an Enterprise Rollup Report, launch the TPC GUI for the TPC master server and log on to the TPC GUI as a TPC superuser or administrator:

1. In the TotalStorage Productivity Center GUI, expand IBM TotalStorage Productivity Center → My Reports → Rollup Reports.

2. Expand either Asset or Capacity.

3. Expand and select one of the reports. The Report Selection window is displayed. Notice the information in the right-most column: Rollup Reports and Asset. Use these reports to view detailed statistics about your computer.

4. You can modify the selection and filter criteria for the report. Click Generate Report.

5. The report is generated and displayed.

6. The Device server on the subordinate server must be running in order for the master server to pull data.


Figure 5-153 illustrates the window used to generate the Asset Information Report by Computer. Notice the information in the right-most column; this information will be displayed in the generated report.

Figure 5-153 Rollup Report sample selected columns

Figure 5-154 on page 529 shows an Agent Asset Rollup report by agents.


Figure 5-154 Sample Rollup Report

These two examples illustrate how you can roll up network-wide summary metrics from multiple TPC servers and report on their storage environment from a network-wide perspective.

5.8 VMware ESX Server supportIn this section, we see how TotalStorage Productivity Center for Data V3.3.2 can be used to see the topology and reports for VMware Virtual Infrastructure.

Refer to 2.2.3, “VMware environment considerations” on page 40 for information about planning for the VMware Virtual Infrastructure, and 4.10, “Configuring TPC communication to VMware” on page 347 for information about configuring TPC for VMware Environment.


As shown in Figure 5-155, the data flow between the VMware environment and the TotalStorage Productivity Center consists of the two connections: the connection of the TotalStorage Productivity Center to the VMware Host Agent of the VMware ESX server through the new VMware VI Data Source, and the connection of the TotalStorage Productivity Center Data agents residing in the VMware virtual machines inside the VMware ESX server.

Figure 5-155 VMware ESX Server communication with TotalStorage Productivity Center


5.8.1 Topology Viewer for VMware Environment The general Topology Viewer Overview contains special information about hypervisors and VMware virtual machines. To look at the Topology Viewer Overview, select IBM TotalStorage Productivity Center → Topology, which displays a window that looks similar to Figure 5-156. Notice the Virtual Computers and hypervisors in the Computers box. Double-click Computers to open the L0 overview.

Figure 5-156 Topology Viewer Overview window showing hypervisor and virtual machines


The L0 overview of Computers shows all computers, virtual computers, and hypervisors (see Figure 5-157). Notice the computer type column on the bottom of the window. Double-click your hypervisor to get to the L2 overview of your hypervisor computer.

Figure 5-157 L0 Computers view showing hypervisor and virtual machines


The L2 Computer window shows detailed information about your hypervisor. You can see information that is separated in the Device, Virtual Computers, and Connectivity tabs. Return to the previous window (Figure 5-158) and double-click one of your virtual computers for the L2 view of a virtual computer.

Figure 5-158 L2 view for hypervisor


The Virtual Computer L2 Overview shows detailed information about Device and Connectivity characteristics (Figure 5-159). The Device tab shows additional controller and virtual machine (VM) disks information. The Connectivity tab shows additional switches information.

Figure 5-159 L2 View for Virtual Machines

LUN Correlation or LUN Definition in TopologyWith IBM TotalStorage Productivity Center V3.3.2, we can see LUN Coronation for VMware ESX Server and virtual machines on it. LUN Correlation allows you to visualize end-to-end mapping of storage from subsystem to volumes assigned to VMware Guest OSs. Figure 5-160 on page 535 shows LUN Correlation in the L2 Overview.


Figure 5-160 LUN Correlation for VMware environment

5.8.2 Reports for VMware EnvironmentTotalStorage Productivity Center for Data V3.3.2 allows you to see various reports for VMware ESX Server. This section gives you an overview of those reports.


Reports for ESX ServerIn the Navigation Tree, select Data Manager → Reporting → Asset → By Hypervisor and click the ESX Server for which you want to see the details.The details will be shown in the right side control pane. The details includes Network Details, Hardware Details, Operating System Details, Disk Details, uptime and probe details (see Figure 5-161).

Figure 5-161 ESX Server details


Expand the ESX Server menu in the Navigation Tree to see the details about Virtual Machines, Controllers, Disks and Filesystem, or Logical Volume Details for that ESX Server (Figure 5-162).

Figure 5-162 VMs, Controllers, Disks and FileSystem details menu for ESX Server


� To see Virtual Machines details, expand the Virtual Machines menu (Figure 5-163). This will show you all the Virtual Machines on the ESX Server, including the one on which a Data Agent is not installed. We will discuss the Virtual Machine reports in more detail in “Reports for Virtual Machines” on page 542.

Figure 5-163 List of VM on ESX Server


� To see the Controllers details for ESX Server, expand the Controller menu. This will list all the controllers on the ESX Server (Figure 5-164). You can see the details of individual controller by expanding the corresponding menu.

Figure 5-164 List of Controllers on an ESX Server


� Expand the Disks sub-menu to get the list of all the disks on ESX Server (Figure 5-165). It will show you the list of all the disks on the ESX Server, including the local disks as well as the disks from storage subsystem.

Figure 5-165 Lists of disks on ESX Server


The right side control pane shows the details about each of the disks. It shows the General Information, Path details, Latest Probe, and Probe History Details for all of the disks and LUN Definition for the disks that are mapped from storage subsystem. LUN Definition or LUN Correlation gives you the information about disk to LUN mapping. The information includes LUN Name, LUN WWN, and Storage SubSystem Details (Figure 5-166). By using LUN Definition, you can discover which disk is mapped to which Storage and LUN.

Figure 5-166 LUN Definition for a disk on ESX Server


� Expand the Filesystem or Logical Volume sub-menu for the ESX Server to see the list of all the filesystems or logical volume on ESX Server (Figure 5-167). The right side control pane shows the details of the filesystem, including filesystem type, mount point, capacity and usage details, and probe and discovery details.

Figure 5-167 Filesystem or Logical Volume details of an ESX Server

Reports for Virtual MachinesTotalStorage Productivity Center for Data V3.3.2 allows you to see various reports for Virtual Machines hosted on a VMware ESX Server. This section gives you an overview of those reports.

Select Data Manager → Reporting → Asset → By Hypervisor → Virtual Machines. This will show all the Virtual Machines hosted on an ESX Server, including the one on which Data agent is not installed.


� For the Virtual Machines on which Data agent is not installed, only limited information is displayed (Figure 5-168). The information that is displayed is the Virtual Machine name, Hypervisor name, VM Configuration File path, OS Details, Processor Count, and RAM size.

Figure 5-168 Information about Virtual Machine on which data agent is not installed


� More detailed reports can be seen for Virtual Machines on which a Data agent is installed. Upon clicking the Virtual Machine name, the right hand control pane gives information about the Virtual Machine, such as VM name, Hypervisor name, VM Configuration file path, Network Address details, hardware details, operating system details, disk capacity details, and probe and discovery details (see Figure 5-169).

Figure 5-169 Detail about Virtual Machine on which Data agent is installed


� You can also see the Controllers, Disks, Filesystem or Logical Volume, Exports or Shares and Monitored Directories details about the Virtual Machine on which the Data agent is installed. Expand the Virtual Machine menu to get to these details (Figure 5-170).

Figure 5-170 Controllers, Disks, FS or LV, Exports and Monitored Directories details for a VM


� Expand the Controllers sub menu for the VM to get the list of controllers. Click the controller to get the corresponding details (Figure 5-171).

Figure 5-171 Controller details for a VM

� Expand the Disks submenu of the VM to get the details about the disks on the VM. It will show you the list of all the disks on the Virtual Machine, including the disks mapped from ESX Server’s local Datastore as well as the disks from storage subsystem (see Figure 5-172 on page 547). The right side control pane shows the details about each of the disks. It shows General Information, Path details, Latest Probe and Probe History Details, Mapping to Hypervisor for all of the disks, and LUN Definition for the disks that are mapped from the storage subsystem.


Figure 5-172 Disk details for a VM


Mapping by Hypervisor shows disk mapping details from VM to hypervisor. It shows Disk name on VM, VM and Hypervisor name, Mapping type, VMDK file name on Hypervisor, and disk name on Hypervisor, as shown in Figure 5-173.

Figure 5-173 Disk mapping details to hypervisor for a VM


LUN Definition or LUN Correlation gives you details about which disk is mapped to which LUN. The information includes LUN Name, LUN WWN, and Storage SubSystem Details, as shown in Figure 5-174. When using LUN Definition, you can discover which disk is mapped to which Storage and LUN.

Figure 5-174 LUN definition for a disk


� Expand the Filesystem or Logical Volumes sub-menu for the VM to obtain the details of the filesystems, as shown in Figure 5-175. The right side control pane shows the details of the filesystem, such as filesystem type, mount point, capacity and usage details, probe, and discovery details.

Figure 5-175 Filesystem details for a VM


Filesystem Capacity reports for ESX Server and VMYou can also see the Filesystem Capacity reports for the ESX Server and VM and discover which data agent is installed. To obtain the Filesystem Capacity reports, select Data Manager → Reporting → Capacity → Filesystem Capacity → By Computer (Figure 5-176).

Figure 5-176 Filesystem Capacity by Computer report filter


Select the column that you want to select and click Generate Report. A Filesystem Capacity report is generated (see Figure 5-177). The report shows the filesystem details of all the VMs on which a Data agent is installed and for the VMware ESX Server.

Figure 5-177 Filesystem Capacity report for VM and ESX Server

Note: You must probe both the ESX Server and the Data agent on the virtual machines before you can generate accurate reports for disk and filesystem capacity. For example, you have an ESX Server that has 100 GB, and 60 GB are allocated to the virtual machine. The virtual machine uses 5 GB of space. Both the ESX Server (H1) and the virtual machine (VC1) have been probed. You also have a physical computer (PC1) that has been probed. The total capacity for the filesystem or disk capacity row includes everything, including virtualized disks and virtual machines, as well as non-virtualized disks and machines.


5.9 Troubleshooting and housekeepingHousekeeping is a key consideration for ensuring that your TotalStorage Productivity Center server performs well and continues to meet the objectives that you had when designing and implementing the original solution.

In this section, we show you regular housekeeping and troubleshooting tasks to ensure that your TotalStorage Productivity Center environment continues to be managed well and, therefore, continues to provide high value to your organization.

5.9.1 Determining the version of Agent ManagerYou can run the GetAMInfo command to determine which version of Agent Manager is installed. To display the version of Agent Manager, complete the following steps:

1. Change to one of the following directories:

– For AIX, Linux, and UNIX: <Agent_Manager_install_directory>/bin

– For Windows: <Agent_Manager_install_directory>\bin

where <Agent_Manager_install_directory> is the directory where the Agent Manager is installed.

2. To display the version for the Agent Manager, run the following command:

– For AIX, Linux, and UNIX: GetAMInfo.sh AgentManager

– For Windows: GetAMInfo.bat AgentManager

3. To display the version for the Agent Recovery Service, run the following command:

– For AIX, Linux, and UNIX: GetAMInfo.sh AgentRecoveryService

– For Windows: GetAMInfo.bat AgentRecoveryService

Note: The application name, AgentManager, is not related to the name of the application server in which you install Agent Manager. For example, if you install the Agent Manager into the application server named server1, the application name remains AgentManager.


4. To display the versions of both the Agent Manager and Agent Recovery Service, run the following command:

– For AIX, Linux, and UNIX: GetAMInfo.sh

– For Windows (see Figure 5-178): GetAMInfo.bat

Figure 5-178 Output from getaminfo.bat command

5.9.2 The Agent Manager toolkit for administratorsIn addition to the commands in <Agent_Manager_install_dir>, the Agent Manager provides a toolkit of “as-is” administration tools. The toolkit commands are in the <Agent_Manager_install_dir>/toolkit/bin directory. Be careful when using these tools, because they have not been translated, and the output of the commands are not translated. They are also subject to change in the future.

The Agent Manager toolkit commands must be run from within a DB2 environment command window. The command HealthCheck verifies the state of the Agent Manager basic functions. This command indicates if the Agent Manager is operational and shows the parameters of the AgentManager configuration. This command must be run from the machine on which the Agent Manager is installed.

To run the HealthCheck command on UNIX and Linux systems, you need to run the script file HealthCheck.sh (on Windows, HealthCheck.bat). The Healthcheck scripts use the JAR file HealthCheck.jar, which contains the Java code for the command.


A useful example of using the HealthCheck command is to display the AgentManager configuration and to verify that the Common agent password that you are using is still valid:

� For Windows: healthcheck -registrationPw changeMe

� For UNIX: ./healthcheck.sh -registrationPw changeMe

where changeMe is the password that you are checking.

Figure 5-179 Output from healthcheck.bat registrationPw command

The LogCollector command gathers the logs and other information needed to debug problems with the Agent Manager. When you run LogCollector, it creates the LogCollector.zip file, which is located in the root directory where the Agent


Manager is installed. This command must be run from the machine on which the Agent Manager is installed. The files are:

� LogCollector.sh: This script runs the LogCollector command on UNIX and Linux systems.

� LogCollector.bat: This script runs the LogCollector command on Windows systems. The script calls the LogCollector.jar file, which is a JAR file that contains the Java code for the command.

5.9.3 Reregistering a Common agentA variety of connectivity and registration problems can sometimes be resolved by forcing the Common agent to register with the Agent Manager again. Before you begin, make sure that you know the current agent registration password.

To reregister a Common agent, follow these steps:

1. Stop the Common agent.

2. Delete the contents of the <common_agent_install_directory>/cert directory on the Common agent system.

3. Copy the agentTrust.jks file from the <Agent_Manager_install_directory>/certs directory on the Agent Manager server to the <common_agent_install_directory>/cert directory on the Common agent.

4. Change the agent registration password, which is saved in an encrypted format, in the endpoint.properties file on the Common agent:

On Windows systems:

a. Change to the Common agent installation directory:

<common_agent_install_directory>

b. Run the following command to change the agent registration password:

encryptPwdInConfFile.bat <agent_registration_password>

The variable <agent_registration_password> is the new agent registration password.

Note: You can run the healthcheck command to confirm the agent registration password.


On UNIX systems:

a. Change to the Common agent installation directory:

cd <common_agent_install_directory>

b. Run the following command to change the agent registration password:

encryptPwdInConfFile.sh <agent_registration_password>

The variable <agent_registration_password> is the new agent registration password.

5. Restart the Common agent.

5.9.4 Connecting a Common agent to a new Agent ManagerIf you have existing Common agents installed in your environment that are tied to an Agent Manager that no longer exists, you can migrate the Common agents to point to a new Agent Manager.

To migrate a Common agent to point to another Agent Manager, follow these steps:

1. Stop the Common agent:

– For Windows: To stop the services on Windows, select Start → Control Panel → Administrative Tools → Services. Stop IBM Tivoli Common agent <directory>. Verify that the Common agent service has stopped. For Windows, check the service in the Windows Services window. You can also check to see if the ports are being used by issuing the following command:

netstat -an

– For UNIX or Linux: Go to the installed directory and issue this command:

/opt/IBM/TPC/ca/endpoint.sh stop

Verify that the Common agent service has stopped. For UNIX, issue the following command:

ps -ef | grep nonstop

You can also check to see if the ports are being used by issuing the following command:

netstat -an

2. Change the endpoint configuration file (endpoint.properties) on the Common agent computer in this directory:

– For Windows: C:\Program Files\IBM\TPC\ca\config

– For UNIX: /opt/IBM/TPC/ca/config


The endpoint.properties file contains address references to hosts performing various functions. Update these addresses (or host names) to point to the Agent Manager. When the Common agent is installed, the installation process will put in the IP addresses (not host names):

AgentConfiguration.Host= CertManagement.Host= AgentQuery.Host= Registration.Host= Registration.domain= Registration.Server.Host= AgentManagerQuery.Host= Config.Server.Host=

There are other entries needed to connect to the Agent Manager. You do not need to change these entries from the default values. If you want to validate these entries, you will find them in the Agent Manager configuration files. The parameters are:

Registration.Server.Port=<new_registration_server_port_number>Registration.Server.ContextRoot=<new_registration_server_context_root>Registration.domain=

3. Delete or remove the certificate files from the Common agent ca/cert directory. As a precaution, create a cert.bak directory and copy the contents of the ca/cert directory to the cert.bak directory.

4. Update the password (if it differs between the Agent Managers). The command is:

<common_agent_install_directory>\jre\bin\java -cp lib\ep_install.jar; lib\ep_common.jar com.tivoli.agent.install.EncrPwdInConfFile Config\endpoint.properties Registration.Server.PW <password>

5. Move or delete the contents of the <common_agent_install_directory>\logs subdirectory.

6. Reset the tivguid if you want, but this reset normally is not needed.

7. Restart the Common agent service:

– For Windows: To start the services on Windows, select Start → Control Panel → Administrative Tools → Services. Start IBM Tivoli Common agent <directory>.

– For UNIX or Linux: Go to the installed directory and issue this command:

/opt/IBM/TPC/ca/endpoint.sh start

You see the ports in use and a message in <common_agent_install_directory>\logs\msgAgent.log that shows the agent connecting to the new Agent Manager and registering successfully. The log ends with the standard “ready for automated e-business” message. You also can see new certificate files in the /cert subdirectory.


5.9.5 Using repocopyThe repocopy tool allows you to make a copy of your TotalStorage Productivity Center database repository. A typical scenario for using this tool is to copy a repository from a test environment to a production environment.

The repocopy tool enables you to export all of the tables in your IBM TotalStorage Productivity Center repository into a text format and then import data into the same or another database using the same repocopy command. For example, you can use this tool to export a repository from an SQL Server instance and import it to an Oracle instance, or you can export from one DB2 instance and import it to another DB2 instance. repocopy is also a useful tool when database tables need to be reviewed by development.

To use the repocopy tool, follow these steps:

1. Go to the following default directory:

– For Windows: C:\Program Files\IBM\TPC\data\server\tools

– For UNIX or Linux: /opt/IBM/TPC/data/server/tools

Important: repocopy is designed as a tool for troubleshooting and analysis, and it is not intended to be used for a backup mechanism.

Never import a repocopy into an existing production TotalStorage Productivity Center database, because this action will cause database corruption, which can have a catastrophic effect on the storage information within your TotalStorage Productivity Center database.


2. Run the repocopy.bat or repocopy.sh command. A window (Figure 5-180) appears. Select Export data from repository tables to export your existing repository data into a comma-delimited file.

Figure 5-180 Running the repocopy command

a. Click Next. For exporting data, IBM TotalStorage Productivity Center processes the repository table into the comma-delimited file that you specify and places it into a file named <tablename>.txt (Figure 5-181). Click Next to continue.

Figure 5-181 Click Next for Import/Export


3. The Connection Properties window displays. In this step, IBM TotalStorage Productivity Center reads the server.config file and determines your current repository and the information for accessing the database. The information detected in the server.config file is displayed in the Connection Properties window within the following fields: Database Types, User name, Password, Driver Class, Driver URL, Database, DB Creator, and Classpath (Figure 5-182). Click Finish.

Figure 5-182 Connection Properties window

4. The window shown in Figure 5-183 appears. Click Run to start the Export.

Figure 5-183 Export settings window


5. When the Export finishes, close the window (Figure 5-184).

Figure 5-184 Export settings window

6. The repocopy utility also has a DOS window running in the background, which shows the progress of the Export function (Figure 5-185 on page 563).


Figure 5-185 Export progress log file


Appendix A. Worksheets

This appendix contains worksheets that are meant for you to use during the planning and the installation of the IBM TotalStorage Productivity Center. The worksheets are meant to be examples. Therefore, you can decide whether you need to use them, for example, if you already have all or most of the information collected somewhere.

If the tables are too small for your handwriting, or you want to store the information in an electronic format, simply use a word processor or spreadsheet application and, using our examples as a guide, create your own installation worksheets.

This appendix contains the following worksheets:

� User IDs and passwords

A


User IDs and passwordsWe created a table to help you write down the users IDs and passwords that you will use during the installation of IBM TotalStorage Productivity Center for reference during the installation of the components and for future add-ons and agent deployment. Use this table for planning purposes.

You need one of the worksheets in the following sections for each machine where at least one of the components or agents of Productivity Center will be installed. This is because you may have multiple DB2 databases or logon accounts and you need to remember the IDs of each DB2 individually.

Server informationTable A-1 contains detailed information about the servers that comprise the TotalStorage Productivity Center environment.

Table A-1 Productivity Center server

In Table A-2, simply mark whether a manager or a component will be installed on this machine.

Table A-2 Managers/components installed

Server Configuration information

Machine

Host name

IP address ____.____.____.____

Manager/component Installed (y/n)?

Productivity Center for Disk

Productivity Center for Replication

Productivity Center for Fabric

Productivity Center for Data

Tivoli Agent Manager

DB2


Worksheet for user IDs and passwordsIn this section, we provide you with a worksheet to help you keep track of user IDs and passwords during the planning and installation of IBM TotalStorage Productivity Center. We also provide a description of the purpose of each one.

At the end of this appendix you will find a worksheet that you can print in order to keep track of your installation user IDs and passwords.

Table A-3 User IDs and passwords for IBM TotalStorage Productivity Center installation

Item Description Your input

DB2 administrator user ID and password

This user ID and password is required to install IBM TotalStorage Productivity Center. On Windows, this user ID must be a member of the DB2ADMNS group and Administrators group. On UNIX, the user ID must be the instance owner of the instance you wish to use. This user ID and password is created when you install DB2.

Certificate authority password

This password allows you to look at the certificate files if you have problems. Specified when you install the Agent Manager.

Common agent registration password

This is the password required by the common agent to register with the Agent Manager. Specified when you install the Agent Manager. You must specify this password when you install the common agent.

Common agent service logon user ID and password

This is for Windows only and is optional. This creates a new service account for the common agent to run under. If your enterprise has a security policy that requires long passwords, the installation can fail. This user ID and password allows you to run under a local account user name and password that meets your enterprise's security policy. This user ID and password will be created if you do not have one.

No default. If this user ID and password does not exist, these will be created at installation time.

Host authentication password

This password is required for:

� The Fabric agent that communicates with the Device Server

� The subordinate server when added to the master server (for enterprise-wide reporting)

Specified when you install the Device Server. You must specify this password when you install the Fabric agent.

This password is created when you install the Device Server.

NAS filer login user ID and password

This is for Windows only. This is the default user name and password used by Data agents during NAS discovery.

Appendix A. Worksheets 567

User IDs and passwords for key files and installationUse Table A-4 to note the password that you used to lock the key file.

Table A-4 Password used to lock the key files

Enter the user IDs and password that you used during the installation in Table A-5. Depending on the selected managers and components, some of the lines are not used for this machine.

Table A-5 User IDs used on this machine

Resource manager registration user ID and password

This is the user ID and password required by the Device server and Data server to register with the Agent Manager. You must specify this user ID and password when you install the Device server or Data server. For information about how to change the user ID and password, see “Changing the registration password for a resource manager” in IBM TotalStorage Productivity Center Installation and Configuration Guide,GC32-1774.

The default user ID is manager. The default password is password.

WebSphere administrator user ID and password

This is the user ID and password required by the Device server to communicate with embedded WebSphere. Embedded WebSphere runs as a Windows Service. The Windows Service runs under the authority of this user ID and password. This user ID and password is only used when you install the Device server.

If this user ID and password does not exist, these will be created at installation time.

Windows Service account and password.

This account and password is valid for Windows only and lets the agent run under this service account.

When you install the IBM TotalStorage Productivity Center agent, you will be able to specify a domain name, which validates the account and password.

Default key file name Key file name Password

agentTrust.jks

Element Default/ recommended user ID

Enter user ID Enter password

DB2 DAS User db2admina


DB2 Instance Owner db2inst1

DB2 Fenced User db2fenc1

Resource Manager managerb

Common Agent AgentMgrb

Common Agent itcauserb

TotalStorage Productivity Center universal user

tpcsuida

IBM WebSphere c

Host Authentication c

a. This account can have any name you choose.b. This account name cannot be changed during the installation.

Element Default/ recommended user ID

Enter user ID Enter password

Appendix A. Worksheets 569

Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.

IBM Redbooks publicationsFor information about ordering these publications, see “How to get IBM Redbooks publications” on page 572. Note that some of the documents referenced here might be available in softcopy only:

� TotalStorage Productivity Center V3.3 Update Guide, SG24-7490

� IBM TotalStorage Productivity Center V3.1: The Next Generation, SG24-7194

� IBM System Storage Solutions Handbook, SG24-5250

TotalStorage Productivity Center documentation

These publications are product documentation:

� IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774

� IBM TotalStorage Productivity Center Messages, GC32-1776

� IBM TotalStorage Productivity Center Problem Determination Guide, GC32-1778

� IBM TotalStorage Productivity Center User’s Guide, GC32-1775

� IBM TotalStorage Productivity Center Workflow User’s Guide, SC32-0101

Online resourcesThese Web sites and URLs are also relevant as further information sources:

� TotalStorage Productivity Center Version 3 Release 3 Supported Product List:




� TotalStorage Productivity Center Version 3 Release 3: Supported Products List - all vendors

http://www-1.ibm.com/support/docview.wss?rs=1133&context=SS8JB5&context=SSWQP2&dc=DB500&q1=HP+XP&uid=ssg1S1002824&loc=en_US&cs=utf-8&lang=en

� TotalStorage Productivity Center Version 3 Release 3 Platform Support: Agents, CLI, and GUI


� TotalStorage Productivity Center Version 3 Release 3 Platform Support: Managed Database Support


� TotalStorage Productivity Center support Web site


� IBM Redbooks publications


How to get IBM Redbooks publicationsYou can search for, view, or download IBM Redbooks publications, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy IBM Redbooks publications or CD-ROMs, at this Web site:

ibm.com/redbooks

Help from IBMIBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services


http://www-1.ibm.com/support/docview.wss?rs=1133&context=SS8JB5&context=SSWQP2&dc=DB500&q1=HP+XP&uid=ssg1S1002824&loc=en_US&cs=utf-8&lang=en




http://www.ibm.com/support/

http://www.ibm.com/support/


http://www.ibm.com/services/

http://www.ibm.com/services/



Index

AAccess Time Summary report 394Active Directory 59Add the root user to the DB2 instance group 190administrative rights

DB2 user 95administrator type users 59advanced copy services 5advanced provisioning 19Agent

install via GUI 64remote install 64

agent 10, 22information 388

agent communication ports 295agent component log 386agent deployment 288

Common Agent logs 324interactive installation 289local installation 288log files 323remote installation 288run scripts 294service 322silent installation 288Solaris 10 system 308unattended (silent) installation 300

agent disk requirements 35agent information 385agent install verification 320Agent Manager

certificates 60change agent ownership 557database connection 128default password 145default user ID 144healthcheck utility 126key file 60reregister agent 556security certificate 116server installation 144server port 9511 144

Agent Manager install

© Copyright IBM Corp. 2009. All rights reserved.

graphical installers 173Agent Manager installation 71, 105Agent Manager Password 117Agent Manager repository 45Agent Manager services

host name 111Agent Manager Toolkit 554agent recommendations 49Agent Recovery Service 113agent registration

confirm password 556agent registration password 60, 85, 118, 277agent remote installation 306agent reregistration 556agent uninstallation procedures 325agents

install path 290NAS filers 40

agents report 467agentTrust.jks file 61, 118AIX install

Agent Manager 239Agent Manager installation 254Agent Manager password 251Agent Manager Registration Port, 246agent registration password 251certificate authority password 250certificates 249create database schema 263DAS user ID 225DAS user window 224database connection type 264database schema 257Database User Information 245DB2 215DB2 fenced user ID 164, 229DB2 Fix Pack 170, 235DB2 instance owner 264DB2 port 50000 273DB2 UDB 216Device server 280downloaded image 258installation media 215keystore file 251

573

NAS discovery 276root user 190, 238Schema name field 265Security roles 274shut down DB2 environment 171, 236SNMP community 276source the DB2 environment 258su - db2inst1 169, 234Tivoli Agent Manager 242Tivoli Agent Manager registry 242TPCDB 264unmount install media 235, 256verify DB2 installation 234VNC Viewer 216

AIX machine information 35alert conditions 431alert disposition 341alert statistics 429Alert Triggering Condition 430alerting 428

facility 24alerts

notification 24SNMP port 341

architectural overview 18ARS.version field 127asset by computer 474asset reporting

reportsasset 452

assetsBy Storage Subsystem 464System-wide 466

automatic file system extension 10

Bbackup and archive 404backup reporting 482batch report type 411batch reports 410

Ccapacity information 472, 477, 494, 497CD layout 73centralized repository 45Certificate Authority file 60certificate authority password 85changing agent configuration 284

CIMOMinteroperability namespace 66manually entering CIMOMs 366

CIMOM componentlog 386

CIMOM configuration 356CIMOM discovery 360CIMOM discovery alert 357CIMOM discovery job 357, 359CIMOM logins 356CIMOM logs 368clients 9commands

netstat -a 71netstat -an 51

Common agent password verification 555Common agent port 51Common agent registration 118Common agent registration password 295Common agent service 322comprehensive reporting 13computer alerts 429computer group 418Computer Uptime report 471computers report 468configuring

TotalStorage Productivity Center for Data 287constraints 442content window 382create a quota 439create truststore 348Custom installation 72, 131

user ID and password rules 80Custom installation component selection 132customer support 68

DData agent 388

install options 317local uninstall 326monitored databases 47remote target 318remote uninstall 330scripts 317uninstall 324

Data agent upgrade 336data flow 19Data Manager


data retention 369logfile retention 342My Reports 393user defined profile 427

Data Manager node 416Data Migration Utility 47Data Path Explorer 511

launch 512MDisk view 514

data retention 369Data server

port 9549 142ports 51

Data server component 6, 48Data Server port 9549 292Data server service 150Data Sources 388Data user levels 58database creation 133Database Migration Utility 46database reporting 372database repository 45database support 13database-managed space 45databases

IBMCDB 45DataManager 21, 24

operating 380, 553DataManager for Chargeback 375DB2

file system ownership 258DB2 Administration Server 94DB2 database

performance 134, 197DB2 database sizing 134, 197DB2 installation 87, 110

administrator group 99default path 94verify installation 103

DB2 instance owner user ID 228DB2 log files 138DB2 password rules 84DB2 user account 95DB2 user and password 133DB2 user IDs 84DB2 user rights 84DB2 window services 104DB2ADMNS group 110db2level command 104

db2profile script 173default database name 45default installation directory 70, 72Device server

port 9550 142Device server component 6Device server port 9550 293Device Server service 150directories

Exports or Shares 460directory alerts 433directory group 419directory grouping 419disk capacity

Network-wide 473Disk Capacity Summary report 397disk report

General 457

Latest Probe 457Paths 457

disk/volume group support 55disks report 469display system properties 35DNS suffix 75domain name system 75Duplicate File report 480

Eendpoint configuration file 557enterprise repository 21Enterprise Rollup reporting

master server 516Enterprise Server Rollup 516ESX Server 41Exports or Shares report 460

Ffilesystem 418, 458

alerts 432extension 10, 54, 447

Filesystem Capacity report 475filesystem group 418filesystems supported 54

Ggenerate a report 398

Index 575

GetAMInfo command 553groups 418GUI applet 280GUI for Web access 151GUID 78gunzip command 240

HHACMP support 16hardware prerequisites 34HealthCheck command 554healthcheck utility 126historical report 476history aggregator 353Host authentication password 143, 312HTTP connection 24hypervisor product 12hypervisors 531

IIBM

Tivoli Enterprise Console 25Tivoli Storage Manager 27

IBM TotalStorage Productivity Centerfor Disk 5for Fabric 4for Replication 5

IBMCDB database 110installation

agent installation 63agent locally 64Agent Manager 70electronic image 148IBM Tivoli Storage Manager 69instructions 69user ID privileges 57user IDs 57

installation licenses 131integration 24

with IBM products 25with ITSM 10

IP address 566IPv6 considerations 42itcauser 296, 316

Jjob

information 392ping 421Scan 423

job scheduler 21

Kkey

configuration 288key file for Agent Manager 60keytool

command syntax 349keytool command 347–348

LLanguage selection window 130launch-in-context feature 15License Agreement window 130Linux

install images 192Linux install 151

agent manager password 183agent recovery service 179agent registration password 183agent scan 210certificate authority password 182Common agent registration password 211DAS user window 158database administrator 196database schema information 197DB2 installation 151DB2 instance owner 163DB2 tools catalog 164DB2 UDB connection 177demonstration certificates 181fenced user window 163groups command 191host communication password 206host name 206IBMCDB database 177NAS Discovery Information 209root user group add 191run a script 210SMTP notification 165start TPC GUI 214Tivoli Agent Manager 174verify DB2 installation 169WebSphere Application Server connection infor-mation 178


Linux space requirements 35local agent uninstall 326log files

CLI 151Data server 150Device server 150GUI 151

LogCollector for Agent Manager 555log-file retention 342logical volumes 459LUN definition 457

MMicrosoft

Cluster Server 23, 452Monitored Directories report 461monitoring 417monitors 13multiple condition alert 432Multiple disk install window 148My Reports node 393

NNAS 12NAS considerations 39NAS discovery 276NAS discovery information 143NAS environment considerations 39NAS filers 39NAS support 23, 55, 441NAS/NetWare 55NAS/NetWare server entry 345Navigation Tree

administrative services 383agent information 385Data Manager node 416Services 384

navigation tree 380NDS trees 39NDS trees discovery 39NetBIOS 78netstat command 52NetWare 22, 355NetWare servers considerations 39network

appliance 441connectivity 62filesystems 54

nslookup 62

Oonline support 68operating DataManager 380, 553operating system type reports 462operator type users 59OS user group grouping 421oslevel command 62overview 1

Ppin list persistence 502ping job 421pinning 502platforms supported 36Policy Management 438

Archive/Backup 449constraints 442quotas 439, 482scheduled actions 447

policy-based management 10ports

Data server 51reserved 72

predefined reports 393Primary DNS suffix 77private pin lists 502privileges for install user ID 57probe job 413

VMware environment 352probe setup 490PROBE_ME file 285profile creation 426ps -ef command 322public communication

port 9513 144

Qquotas 343, 439

RRDBMS 47, 373RDBMS Logins 489Redbooks Web site

contact us xiiiregister a database 488

Index 577

registered agent availability 471RegistrationPW parameter 126related publications 571removed resource retention 370repocopy tool 559Reporting

capacity 472, 494, 497filesystem capacity 475groups 452historical report 476

Reporting facility 450reporting for databases 486reports

Access File Summary 399Access Time Summary 394agent availability 471backup 482batch output 412By Computer 453By Storage Subsystems 464Computers 468data paths 511disk capacity 397Disk Defects 399Most at Risk Files 401Most Obsolete Files 407Oldest Orphaned Files 407Probe History 457standardized 7Storage Access Time 399Storage Availability 408Storage Capacity 408Storage Modification Times 401subsystem 11system 393System-wide 466Total Free Space 409usage 477usage reporting 477Usage violations 482User Quota Violations 408User Space Usage 409Virtual Machines 542Wasted Space 410

reserved ports 72residency program xiiiResource Manager 569role-based administration 29role-based security 58

role-based users 59Rollup Report

data tables 517generation 524

Rollup Reportingsubordinate servers 516test TPC Server 520

Rollup Reporting categories 523

Sscan agent administration 344Scan job 423Scan job alerts 432–433scheduled actions 447scheduler 385Scheduler component log 386Scheduler.config file 49schema name 134, 197script against monitored server 447scripts 448scripts for Data agent 317Secure Sockets Layer (SSL) 24security

considerations 29security certificates 60Security Certificates window 116server

recommendations 48server component log 386server.config file 49service accounts 61service log 386Service status 386shutdown 388silent install response file 300SMIS 11SMI-S Array Reporting 30SMI-S support 17SNIA CTP Certification 30SNMP

MIB 24trap 24

software prerequisites 36space-efficient volumes

DS8000 16standardized reports 7storage subsystems 56su command 169, 234


subordinate server 516subsystem reporting 11supported systems 29system reports 393system-managed space 45

Ttablespace 371tablespace considerations 265TagmaStore CIM agent 15tape library support 56tar command 240TCP/IP ports 49Tivoli Common Agent Services 27, 30Tivoli Provisioning Manager 13Tivoli Storage Manager 449

backup job 450Tivoli Storage Manager Server

backup and archive 404Topology Viewer 11, 501

Context Sensitive 511Data Path Explorer 511hypervisor support 531integrated reports 504link to alerts 505link to reports 507pin list feature 502pin list persistence 502pinning 502virtual computers 533

TotalStorage Productivity Center 565Assistant 17CIMOM configuration 356component install 129Data server 6Device server 6GUI login 280Install using CD 257license 131overview 2physical structure 4structure 3

TotalStorage Productivity Center for Dataarchitecture 8clients 9Data agent 9Data manager 9overview 7

Web server 9TPC Data agent

VMware considerations 41TPC for Data

architecture 17TPC for Replication 5TPC GUI launch 281TPC Server housekeeping 553TPC subordinate servers 521TPC Superuser 142TPCD.config file 17TPCDB database 142TPCDB default database name 45Trace log files 387TSM backup 404, 482TSM required backup storage 484TSRMsrv1 user ID 143Typical installation 72, 92

user ID and password rules 79

Uuniversal agent 14usage

reporting 477violations reporting 482

user group 421user grouping 420user ID 565, 568user interface 21User Rights Assignments 58

Vverify installation 126, 138VMWare

Mapping to Hypervisor 548VMware

Controllers details 539data sources 41ESX Server disks 540Fabric agent 42Filesystem Capacity 551Filesystem report 550Hypervisor Alerts 352, 434LUN Correlation 541LUN Definition 541probe job 352VI Data Source 12Virtual Machines 542

Index 579

VirtualCenter 12VMware ESX Server

TPC configuration 347VMware server

keytool command 347volume groups 458volume managers 55

WWeb server 9WebSphere Application Server 30

Connection Information 246Windows domain 59Windows Services 61Windows space requirements 35

XX Window System display 216


(1.0” spine)0.875”<

->1.498”

460 <->

788 pages

Deployment Guide Series: IBM

TotalStorage Productivity Center for Data

®

SG24-7140-03 ISBN 0738432806

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

®

Deployment Guide Series:IBM TotalStorage Productivity Center for Data

Learn the functions and reporting capabilities of TPC for Data

Install on and configure supported platforms

Includes planning and deployment information

IBM TotalStorage Productivity Center for Data (Data Manager) is a comprehensive file and capacity management solution for heterogeneous storage environments. It includes enterprise-wide reporting and monitoring, policy-based management, and automated capacity provisioning for Direct Attached Storage (DAS), Network Attached Storage (NAS), and storage area network (SAN) environments. Data Manager, Data Manager for Databases, and Data Manager for Chargeback let you improve storage utilization, plan for future capacity, and ensure availability by providing storage on demand for filesystems.

This IBM Redbooks publication is intended for administrators and users who are installing and using IBM TotalStorage Productivity Center for Data. It provides an overview of the product and its functions. It describes the hardware and software environment required and provides a step-by-step installation procedure. Customization and usage information is also provided. The reader needs to have a basic understanding of storage concepts, network topologies, communication protocols, and a basic understanding of the IBM TotalStorage Productivity Center product.

This book focuses on the TotalStorage Productivity Center for Data component as an integral part of the TotalStorage Productivity Center product.

Back cover




deployment guide series ibm total storage productivity center for data sg247140

Technology

totalstorage productivity centerv3

totalstorage productivity center

totalstorage productivity center

totalstorage productivity center

totalstorage productivity center

totalstorage productivity center

totalstorage productivity center

magnifying glass icon