Deployment guide series ibm total storage productivity center for data sg247140
Upcoming SlideShare
Loading in...5
×
 

Deployment guide series ibm total storage productivity center for data sg247140

on

  • 923 views

 

Statistics

Views

Total Views
923
Views on SlideShare
923
Embed Views
0

Actions

Likes
1
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Deployment guide series ibm total storage productivity center for data sg247140 Deployment guide series ibm total storage productivity center for data sg247140 Document Transcript

  • Front coverDeployment Guide Series:IBM TotalStorageProductivity Center for DataLearn the functions and reportingcapabilities of TPC for DataInstall on and configuresupported platformsIncludes planning anddeployment information Mary Lovelace Alejandro Berardinelli Kamalakkannan Jayaraman Nidhi Khatoribm.com/redbooks
  • International Technical Support OrganizationDeployment Guide Series: IBM TotalStorageProductivity Center for DataJune 2009 SG24-7140-03
  • Note: Before using this information and the product it supports, read the information in “Notices” on page ix.Third Edition (June 2009)This edition applies to Version 3, Release 3.3 of IBM TotalStorage Productivity Center for Data(product number 5608-VC3).© 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.
  • Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi The team that wrote this IBM Redbooks publication . . . . . . . . . . . . . . . . . . . . . xi Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv June 2009, Third Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 1 1.1 What is IBM TotalStorage Productivity Center . . . . . . . . . . . . . . . . . . . . . . 2 1.1.1 TotalStorage Productivity Center structure . . . . . . . . . . . . . . . . . . . . . 3 1.2 TotalStorage Productivity Center for Data overview . . . . . . . . . . . . . . . . . . 7 1.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.3.1 What is new in TotalStorage Productivity Center V3.3.2 . . . . . . . . . 14 1.4 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.4.1 Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.4.2 Schema of interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.4.3 Data Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 1.4.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 1.4.5 Integration points with TEC and IBM Tivoli Storage Manager . . . . . 24 1.4.6 Tivoli Common agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 1.4.7 Role-based administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 1.5 Supported levels for Version 3 Release 3 . . . . . . . . . . . . . . . . . . . . . . . . . 29 1.6 System Storage Productivity Center (SSPC) . . . . . . . . . . . . . . . . . . . . . . 31 Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.1 Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.1.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.1.2 Disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.2 Software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.2.1 Novell NetWare considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 2.2.2 NAS environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 2.2.3 VMware environment considerations . . . . . . . . . . . . . . . . . . . . . . . . 40 2.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 . . . . . . . . . . . . . . . . . . . . . . . . . . 45 2.3.2 Agent Manager database repository . . . . . . . . . . . . . . . . . . . . . . . . . 45 2.3.3 SMS or DMS tablespace type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 2.3.4 Database Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2.3.5 Data agent-monitored databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 2.4 Pre-installation steps for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 2.4.1 Installable components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 2.4.2 Order of component installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 2.4.3 Server recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 2.4.4 Installation port requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 2.4.5 Supported filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2.4.6 Supported network filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2.4.7 Support for NAS/NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 2.4.8 Disk and volume group support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 2.4.9 Storage subsystem support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 2.4.10 Tape library support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 2.5 User IDs and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 2.5.1 User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 2.5.2 Increasing user security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 2.5.3 Certificates and key files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 2.6 Services and service accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 2.7 Analyzing and defining environment requirements . . . . . . . . . . . . . . . . . . 62 2.8 Agent installation methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 2.8.1 Local installation of the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 2.8.2 Remote agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 2.8.3 Virtual I/O Server agent installation. . . . . . . . . . . . . . . . . . . . . . . . . . 65 2.9 Interoperability namespace summary table. . . . . . . . . . . . . . . . . . . . . . . . 66 2.10 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Chapter 3. Installing IBM TotalStorage Productivity Center for Data . . . . 69 3.1 Installing TotalStorage Productivity Center . . . . . . . . . . . . . . . . . . . . . . . . 70 3.1.1 Installing Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 3.1.2 Installing Agent Manager on Windows . . . . . . . . . . . . . . . . . . . . . . . 71 3.1.3 Typical installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3.1.4 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3.1.5 CD layout and components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 3.1.6 Configuration considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 3.2 Pre-installation steps for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.2.1 Verify the primary domain name systems . . . . . . . . . . . . . . . . . . . . . 75 3.2.2 Activate NetBIOS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 3.2.3 Using and defining user IDs and passwords . . . . . . . . . . . . . . . . . . . 79 3.3 Windows installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 3.3.1 DB2 installation for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87iv Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3.3.2 Agent Manager installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 3.3.3 Install TotalStorage Productivity Center components . . . . . . . . . . . 129 3.3.4 Installing the Data server, Device server, GUI, and CLI . . . . . . . . . 1393.4 Linux installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 3.4.1 Installing DB2 Version 9 on a Linux platform . . . . . . . . . . . . . . . . . 151 3.4.2 Verifying the DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 3.4.3 Installing the DB2 Fix Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 3.4.4 Installation of the Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 173 3.4.5 Install TotalStorage Productivity Center V3.3 database schema . . 190 3.4.6 Install TPC V3.3 Data server, Device server, CLI, and GUI . . . . . . 2013.5 AIX installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 3.5.1 DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 3.5.2 Verifying the DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 3.5.3 Installing the DB2 Fix Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 3.5.4 Agent Manager installation for AIX . . . . . . . . . . . . . . . . . . . . . . . . . 239 3.5.5 Install TotalStorage Productivity Center V3.3 database schema . . 257 3.5.6 Install TPC V3.3 Data server, Device Server, CLI and GUI . . . . . . 2683.6 GUI for Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 3.6.1 Launch the TotalStorage Productivity Center GUI . . . . . . . . . . . . . 2813.7 Changing the agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Chapter 4. Configuring IBM TotalStorage Productivity Center for Data. 2874.1 Agent deployment options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 4.1.1 Local installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 4.1.2 Remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2884.2 Local installation of Data and Fabric agents . . . . . . . . . . . . . . . . . . . . . . 289 4.2.1 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 4.2.2 Unattended (silent) installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3004.3 Remote installation of Data agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 4.3.1 Preparing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . 307 4.3.2 Performing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . 3084.4 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 4.4.1 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3234.5 Uninstalling the Data agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 4.5.1 Remote uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 4.5.2 Local uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 4.5.3 Remote agent uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3304.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 . . . . . . . . . . . . . . . . . . . . 347 4.11 History aggregator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 4.11.1 Data Manager NetWare tree logins. . . . . . . . . . . . . . . . . . . . . . . . 355 4.12 Data Manager CIMOM logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 4.12.1 Configuring CIMOMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 4.13 Data Manager resource history retention . . . . . . . . . . . . . . . . . . . . . . . 369 4.13.1 Removed resource retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 4.13.2 Resource history retention for databases . . . . . . . . . . . . . . . . . . . 371 4.13.3 Removed resource retention for databases . . . . . . . . . . . . . . . . . 372 4.13.4 Adding databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 4.13.5 Configuring chargeback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Chapter 5. Operations and reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 5.1 Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 5.1.1 The user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 5.1.2 Administrative services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 5.2 IBM TotalStorage Productivity Center menu reports . . . . . . . . . . . . . . . . 392 5.2.1 Predefined reports under the My Reports node . . . . . . . . . . . . . . . 392 5.2.2 Batch reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 5.2.3 Probe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 5.2.4 External Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 5.3 Data Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 5.3.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 5.3.2 Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 5.3.3 Policy Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 5.4 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 5.4.1 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 5.4.2 Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 5.4.3 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 5.4.4 Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 5.4.5 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 5.4.6 Usage violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 5.4.7 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 5.5 Reporting for databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 5.5.1 Register the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 5.5.2 Set up probes and scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 5.5.3 Database capacity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 5.5.4 Database usage reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 5.6 Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 5.6.1 Pin list persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 5.6.2 Link to reports/alerts from the Topology Viewer . . . . . . . . . . . . . . . 504 5.6.3 Context Sensitive Reporting and Data Path Explorer . . . . . . . . . . . 511 5.7 Enterprise Server Rollup function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516vi Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 5.7.1 Rollup Reporting recommendations . . . . . . . . . . . . . . . . . . . . . . . . 516 5.7.2 Creating Rollup reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 5.7.3 TotalStorage Productivity Center server probe process . . . . . . . . . 521 5.7.4 Generating TotalStorage Productivity Center V3.3 Rollup Reports 5235.8 VMware ESX Server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 5.8.1 Topology Viewer for VMware Environment . . . . . . . . . . . . . . . . . . . 531 5.8.2 Reports for VMware Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 5355.9 Troubleshooting and housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 5.9.1 Determining the version of Agent Manager. . . . . . . . . . . . . . . . . . . 553 5.9.2 The Agent Manager toolkit for administrators . . . . . . . . . . . . . . . . . 554 5.9.3 Reregistering a Common agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 5.9.4 Connecting a Common agent to a new Agent Manager . . . . . . . . . 557 5.9.5 Using repocopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559Appendix A. Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565User IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Server information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Worksheet for user IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 567 User IDs and passwords for key files and installation . . . . . . . . . . . . . . . . 568Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571TotalStorage Productivity Center documentation . . . . . . . . . . . . . . . . . . . . . . 571Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Contents vii
  • viii Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • NoticesThis 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. Consultyour 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 IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the usersresponsibility 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 licenseinquiries, 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 suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof 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 madeto the information herein; these changes will be incorporated in new editions of the publication. IBM maymake improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials 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 withoutincurring any obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirmthe accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe 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 themas 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 businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which thesample 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
  • TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. These and other IBM trademarkedterms 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 waspublished. Such trademarks may also be registered or common law trademarks in other countries. A currentlist of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtmlThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: AIX 5L™ GPFS™ System p® AIX® HACMP™ System Storage™ BladeCenter® IBM® System x® DB2 Universal Database™ NetView® System z® DB2® POWER5™ Tivoli Enterprise Console® DS4000® POWER6™ Tivoli® DS6000™ POWER® TotalStorage® DS8000® Redbooks® WebSphere® Enterprise Storage Server® Redbooks (logo) ® z/OS® FlashCopy® System i®The following terms are trademarks of other companies:Network Appliance, WAFL, FlexVol, Data ONTAP, NetApp, and the NetApp logo are trademarks or registeredtrademarks 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 andother countries.Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/orits affiliates.QLogic, and the QLogic logo are registered trademarks of QLogic Corporation. SANblade is a registeredtrademark in the United States.Red Hat, and the Shadowman logo are trademarks or registered trademarks of Red Hat, Inc. in the U.S. andother countries.VMware, the VMware "boxes" logo and design are registered trademarks or trademarks of VMware, Inc. in theUnited 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, andthe 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 ofIntel 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
  • 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 publication This 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 Eggli Stefan Lein Marcus Standau TotalStorage Productivity Center IBM Redbooks publication authors Elizabeth Purzer, Worldwide Tivoli Channels Program Manager Joe Gatti, Tivoli Storage SWAT Team Doug Dunham, former Tivoli Storage SWAT Team IBM Software Group, Tivoli Jason Bamford, EMEA NR - Storage Software SpecialistBecome a published author Join 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.htmlComments welcome Your 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
  • Send your comments in an e-mail to: redbook@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400xiv Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Changes for SG24-7140-03 for Deployment Guide Series: IBM TotalStorage Productivity Center for Data as 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
  • 1 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© Copyright IBM Corp. 2009. All rights reserved. 1
  • 1.1 What is IBM TotalStorage Productivity Center IBM 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 structure The 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 structure TotalStorage 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 Data TotalStorage 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.4 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • TotalStorage Productivity Center for DiskTotalStorage Productivity Center for Disk brings in the Performance Managerfeature and can enable device configuration and management of supportedSAN-attached devices from a single console.TotalStorage Productivity Center for ReplicationThe basic functions of TotalStorage Productivity Center for Replication aredesigned to provide management of the advanced copy services for the IBMSystem Storage DS8000®, IBM TotalStorage Enterprise Storage Server® (ESS)Model 800, IBM System Storage DS6000™, and the IBM System Storage SANVolume Controller (SVC). The advanced copy services include IBM FlashCopy®,Metro Mirror, and Global Mirror capabilities.TotalStorage Productivity Center for Replication focuses on automatingadministration and configuration of the advanced copy services, operationalcontrol (starting, suspending, and resuming) of copy services tasks, andmonitoring 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. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 5
  • 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.6 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 overview TotalStorage 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 Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 7
  • 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 plan8 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • the purchase of additional capacity in a planned, proactive manner rather thanjust 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. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 9
  • 1.3 Features In this section, we describe the significant features of TotalStorage Productivity Center for Data. Policy-based management TotalStorage 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 extension Through 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 integration With 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.10 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Subsystem reportingTotalStorage Productivity Center for Data gathers and reports on disksubsystems. The information includes physical characteristics, such as thedrive’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 thefollowing tasks (subject to the vendor’s implementation of Storage ManagementInitiative 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) reportingEnterprise rollup reportingTotalStorage Productivity Center for Data can enable a storage administrator touse a single interface to generate reports based on data collected by multipleTotalStorage Productivity Center servers. As a storage administrator, you canperform 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 atleast one TotalStorage Productivity Center Standard Edition server configured asa master TPC Server. This server is configured to collect rollup information fromsubordinates. The master server communicates with the subordinate serversusing the Device server application programming interface (API).Topology ViewerThe IBM TotalStorage Productivity Center Topology Viewer is designed toprovide an extended graphical topology representation of the physical and logicalresources (for example, computers, fabrics, and storage subsystems) in yourstorage environment. In addition, the Topology Viewer depicts the relationshipsamong resources (for example, the disks comprising a particular storagesubsystem). Detailed, tabular information (for example, attributes of a disk) isalso provided. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 11
  • 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 support TotalStorage 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 support The 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.12 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Advanced provisioningTotalStorage Productivity Center and Tivoli Provisioning Manager Workflowautomation can reduce provisioning time from hours to minutes and significantlysimplify the task of provisioning new storage capacity. This automation isespecially valuable when adding storage provisioning to existing automatedserver provisioning tasks, such as deploying operating systems, software, andnetwork resources.Comprehensive reportingWith a wide variety of predefined reports, from summaries to detailed reports onstorage assets, you can optimize storage, minimize downtime, and streamlinestorage management.Monitoring and alertsTotalStorage Productivity Center for Data monitors storage assets and discoversnewly added storage resources on your network with centralized administrationfrom a Single graphical user interface. TotalStorage Productivity Center for Dataallows 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 orMicrosoft® Windows Event log when certain conditions occur.Database supportTotalStorage Productivity Center for Data manages the storage assets withinyour database application allowing you to identify the fastest growing databases,spot potential trouble areas, reclaim unused space, and predict future storageneeds.Chargeback supportTotalStorage Productivity Center for Data offers an end-to-end system forinvoicing your cost centers based on their storage usage. TotalStorageProductivity Center for Data makes your data owners aware of and accountablefor their data usage, helping to keep storage costs distributed accurately acrossan organization. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 13
  • 1.3.1 What is new in TotalStorage Productivity Center V3.3.2 TotalStorage Productivity Center V3.3.2 adds the following new features, functions, and enhancements. Internet Protocol Version 6 IBM 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 Server TotalStorage 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.1 TotalStorage 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 agent A 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>toolTPCUA.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.14 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • For more information about IBM Tivoli Monitoring and Tivoli Enterprise Portal, goto the following address:http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc==/com.ibm.itm.doc/toc,.xmlHitachi Data Systems TagmaStoreTotalStorage Productivity Center now supports the Hitachi Data SystemsTagmaStore Common Information Model (CIM) agent V5.8. This version of theCIM Agent supports only the Array Profile and not the Virtualizer Profile.However, IBM TotalStorage Productivity Center supports the TagmaStore as aStorage Virtualizer. IBM TotalStorage Productivity Center can display informationfor virtual disks and local disks.VMware Virtual InfrastructureVMware ESX Server support was provided in TotalStorage Productivity CenterV3.3.0. With TotalStorage Productivity Center V3.3.2, additional support hasbeen 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 theTotalStorage Productivity Center graphical user interface (GUI) on the localworkstation using Java™ Web Start. The TotalStorage Productivity Center GUImust have been previously installed on the local workstation. Thelaunch-in-context feature downloads the latest version of the GUI on the localworkstation if an older version has been downloaded, or if the IBM TotalStorageProductivity Center GUI has not been previously downloaded. If the latestversion 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. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 15
  • 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 AIX TotalStorage 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 volumes TotalStorage 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.16 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • SMI-S support TotalStorage 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 Solaris You 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 supported TotalStorage 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 Architecture TotalStorage 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. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 17
  • 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.18 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 repository1.4.1 Data flow Figure 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 Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 19
  • 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 flow1.4.2 Schema of interactions On 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.20 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 interface The user interface (UI) enables users to request information and then generate and display reports based on that information. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 21
  • 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. 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. Agents Agents 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.22 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • – 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 onevery cluster node machine.IBM Storage Resource Manager Server Server Data JDBC Repository Scheduler SLP TCP/IPAgents CM Agent Disk Storage CIM/OM Host TCP/IPProxy Agents SNMP, NFS, CIFS, NCP LUN File and Application Print Server Server Enterprise Storage ServerFigure 1-5 High-level architecture Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 23
  • Agent Manager Agent 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 Manager In 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 notification The 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. SNMP For 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.24 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • The SNMP MIB can be found in the file in the default Data Manager installationdirectory: For Windows: Program FilesIBMTPCDatasnmptivoliSRM.mib For UNIX or Linux: opt/IBM/TPC/Data/snmp/tivoliSRM.MIBThe MIB is provided for use by your SNMP management console software (forexample, IBM Tivoli NetView® or Hewlett-Packard (HP) Openview). This MIBallows you to better view Data Manager-generated SNMP traps from within yourmanagement console software.For sending SNMP traps, there must be an SNMP service installed and runningon the Data Manager server. To check if there is an installed and running SNMPservice, 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 ispublic.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), whichallows TEC to consider TotalStorageProductivity Center for Data alerts in causalanalysis for problems. TEC is added as a destination for alerts, in addition to theSimple Network Management Protocol (SNMP) Trap and the Windows EventLog. The event definitions are specified in the tivoliSRM.baroc file (provided byData Manager), which is provided on the Data Manager installation CD. ThetivoliSRM.baroc file must be loaded to the active rule base running on the TECserver. Based on the event definitions, the TEC administrator can write its owncorrelation and automation rules for events sent by Data Manager. You have toprovide the TEC server name and the TEC port to start sending events to theTEC server. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 25
  • 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.Figure 1-6 Edit Alert Disposition window26 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Integration with Tivoli Storage Manager Integration 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. Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 27
  • 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. Device Data Server Server Resource Resource Manager Manager Agent Manager IBMCDB Registration Service Ports: 9511 - registration 9512 - authentication Holds the Recovery Services 9513 - updates registration of all agents and resource managers Ports: 80 - recovery 9513 - alternate for recovery Application Server Common Agent Data Agent Fabric Agent 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.28 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 1.4.7 Role-based administration This 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 alerts1.5 Supported levels for Version 3 Release 3 For 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: http://www-01.ibm.com/support/docview.wss?rs=1103&uid=ssg1S1003285 Chapter 1. Introduction to IBM TotalStorage Productivity Center for Data 29
  • 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 advance The 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.30 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 1. Introduction to IBM TotalStorage Productivity Center for Data 31
  • 32 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 2 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.© Copyright IBM Corp. 2009. All rights reserved. 33
  • 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 Hardware For 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.34 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 2.1.2 Disk space The 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 Data agent and GUI Agent Manager server, database Fabric agent V1.3.2 schema, and command-line interface (CLI) IBM AIX 5L V5.1 No Yes with AIX No No (32-bit) 5100-05 maintenance level IBM AIX 5L V5.1 No Yes in 32-bit No No (64-bit) compatibility mode with AIX 5100-05 maintenance level IBM AIX 5L No Yes with AIX No No (32-bit) 5100-05 maintenance level IBM AIX 5L No Yes in 32-bit No No (64-bit) compatibility mode with AIX 5100-05 maintenance level IBM AIX 5L V5.2 No Yes with AIX No No (32-bit) 5200-02 maintenance level IBM AIX 5L V5.2 No Yes in 32-bit No No (64-bit) compatibility mode with AIX 5200-02 maintenance level IBM AIX 5L V5.3 Yes with AIX Yes with AIX Yes Yes (32-bit) 5300-01 5300-01 maintenance level maintenance level and APAR IY70336 and APAR IY7033636 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Platforms Data server, Device Data agent and GUI Agent Manager server, database Fabric agent V1.3.2 schema, and command-line interface (CLI)IBM AIX 5L V5.3 Yes in 32-bit Yes in 32-bit Yes Yes in 32-bit(64-bit) compatibility mode compatibility mode compatibility mode with AIX 5300-01 with AIX 5300-01 maintenance level maintenance level and APAR IY70336 and APAR IY70336IBM AIX V6.1 Yes Yes Yes Yes(32-bit)IBM AIX V6.1 Yes in 32-bit Yes in 32-bit Yes Yes in 32-bit(64-bit) compatibility mode compatibility mode compatibility modeSolaris 8 No Yes No NoSolaris 9 No Yes No NoSolaris 10 No Yes (agent must No No run in global zone; non-global or local zone is not supported.)HP-UX 11 and 11i No Data agent, Fabric No No agent on HP-UX 11iHP-UX 11 and 11i.2 No Yes No NoWindows 2000 No Yes Yes NoAdvanced ServerWindows 2000 No Yes Yes NoDatacenterWindows Server® Yes Yes Yes Yes2003 Standard EditionWindows Server 2003 Yes Yes Yes YesEnterprise EditionRed Hat Enterprise Yes Yes Yes YesLinux AS Version 3.0on System x Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 37
  • Platforms Data server, Device Data agent and GUI Agent Manager server, database Fabric agent V1.3.2 schema, and command-line interface (CLI) Red Hat Enterprise No Data agent No No Linux AS Version 3.0 on System p on POWER5™ Red Hat Enterprise No Data agent No No Linux AS Version 3.0 on System i on POWER® 5 Red Hat Enterprise Yes Yes Yes Yes Linux AS Version 4.0 on System x United Linux 1.0 on No Data agent No Yes System x United Linux 1.0 on No Data agent No Yes System z SUSE LINUX No Data agent No Yes Enterprise Server 8, System p on POWER, 4, and System x SUSE LINUX No Data agent runs on No Yes Enterprise Server 9, all series; Fabric System x, System p on agent runs on POWER 5, System i on System x only. POWER 5, and System z Supported Guest O.S. No Data agent No Yes on VMware ESX Environment38 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 2.2.1 Novell NetWare considerations To 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 considerations This section contains the requirements for installing and running Data Manager within an NAS environment. Agent requirements When 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). Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 39
  • 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. 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 considerations IBM 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.)40 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. 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 with Service 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.Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 41
  • Attention: There is no need to install a Data agent on the VMware ESX server itself. This feature is not supported. 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 – IBM System Storage DS6000 – IBM System Storage DS8000 – 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 considerations TotalStorage 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.42 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Installation scenarios for TotalStorage Productivity Center We illustrate the scenarios and the general steps when installing the product. IPv6-only installation scenario In 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.Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 43
  • IPv6 and IPv4 (dual stack) installation scenario Dual 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=ssg1S100328544 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 2.3.1 Data Manager database repository Data 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 repository The 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. 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.2.3.3 SMS or DMS tablespace type At 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 Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 45
  • 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 Utility You 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.46 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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/tpc2.3.5 Data agent-monitored databases The 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 Sybase2.4 Pre-installation steps for Windows The 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 Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 47
  • 2.4.1 Installable components After 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. 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.4.2 Order of component installation Install the components in the following order: 1. DB2 2. Agent Manager 3. TotalStorage Productivity Center components2.4.3 Server recommendations The 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).48 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. 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.2.4.4 Installation port requirements IBM 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 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=Yes 9510 Session Initiator=No Outbound Inbound Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 49
  • Component Server perspective Firewall port Agent perspective Agent Manager - secure SSL Session Initiator=No 9511 Session Initiator=Yes Registering agents Inbound Outbound Registering resource manager Agent Manager - secure SSL with Session Initiator=Yes 9512 Session Initiator=No client authentication Inbound and Inbound and Providing configuration updates Outbound Outbound Renewing and revoking certificates Querying the registry for agent information Requesting ID resets Agent Manager Session Initiator=No 9513 Session Initiator=Yes Requesting updates to the Inbound Outbound certificate revocation list Requesting Agent Manager information Downloading the truststore file Alternate port for the Agent Recovery Service Common agent (No access N/A 9514 Local to Server needed) Common agent (No access N/A 9515 Local to Server needed) Common Information Model N/A 5988 N/A Object Manager (CIMOM) HTTP CIMOM HTTPS N/A 5989 N/A Agent Recovery Service Session Initiator=No 80 Unsecured connection Inbound for Agent Recovery Service action Push UNIX Session Initiator=Yes SSH(22) Session Initiator=No Outbound Inbound and Outbound Push Windows Session Initiator=Yes NetBIOS Session Initiator=No Outbound sessions Inbound and service (139) Outbound Push UNIX Session Initiator=Yes RSH (514) Session Initiator=No Outbound Inbound and Outbound50 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Component Server perspective Firewall port Agent perspectivePush UNIX Session Initiator=Yes REXEC (512) Session Initiator=No Outbound Inbound and OutboundPush UNIX Session Initiator=Yes 601 N/A InboundPush All Session Initiator=Yes High ports Session Initiator=No Inbound 3000+ Inbound and OutboundPush All Session Initiator=Yes TPC for Data N/A Inbound server 2078Simple Network Management N/A 162 N/AProtocol (SNMP) Listener PortService Location Protocol (SLP) N/A 427 N/A 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. Note: To list the ports in use, run the following commands: For Windows: netstat -an For UNIX and Linux: netstat -an | grep LISTEN Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 51
  • 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 sample52 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 2-2 netstat -ano sampleChapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 53
  • 2.4.5 Supported filesystems TotalStorage 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®. Note: Filesystem extension is supported for JFS filesystems running on AIX 5L V5.1 and VxFS filesystems running on Sun Solaris 2.8.2.4.6 Supported network filesystems Data 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 clients54 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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.22.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. Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 55
  • 2.4.9 Storage subsystem support TotalStorage 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: http://www-01.ibm.com/support/docview.wss?rs=1133&uid=ssg1S10031182.4.10 Tape library support IBM 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.56 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 security This 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 IDs This 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. Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 57
  • 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 security The 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 users There 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.58 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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>.Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 59
  • 2.5.3 Certificates and key files A 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 FilesIBMAgentManagercerts. In a UNIX or Linux environment, the default directory is /opt/IBM/AgentManager/certs. Agent Manager certificates The 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). 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. 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.60 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Comment account DB2 N/A db2admin The account needs to be part of the Administrators and DB2ADMNS groups. Agent Manager IBM WebSphere LocalSystem You need to set this service to start Application Server V5 - automatically, after the installation. Tivoli Agent Manager Common agent IBM Tivoli Common agent itcauser N/A. - C:Program FilesIBMTPCca Productivity IBM TotalStorage TSRMsrv1 N/A. Center for Data Productivity Center - Data server Productivity IBM WebSphere LocalSystem N/A. Center for Fabric Application Server V5 - Fabric Manager Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 61
  • 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.62 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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: http://www-01.ibm.com/support/docview.wss?uid=ssg1S10032852.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. Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 63
  • You can install the agent either locally or remotely.2.8.1 Local installation of the agent There are two methods to install an agent locally on a server that contains a storage subsystem. Installation using GUI To 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 line The 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 installation You 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_namec$. 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.64 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 installation You can use TotalStorage Productivity Center agents to gather information about Virtual I/O Servers. Planning for the Virtual I/O Server configuration This 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. Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 65
  • 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 agents The 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.66 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Important: When providers release new versions of their products, these values can change. Check the provider’s documentation for that provider’s interop namespace. Table 2-4 Interoperability namespace summary 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.Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data 67
  • 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.68 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3 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© Copyright IBM Corp. 2009. All rights reserved. 69
  • 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 FilesIBM... For UNIX and Linux: /opt/IBM/... You can change this path during the installation setup.3.1.1 Installing Agent Manager The 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).70 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Number Retain most recent Retain for seven Retain for 14 days of agents only days Average Max. Average Max. Average Max. Rows Rows Rows Rows Rows 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 Mb3.1.2 Installing Agent Manager on Windows Before 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 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 FilesIBM... 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 installation The 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 installation The 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.72 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3.1.5 CD layout and components In 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 content The 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 73
  • For information about the deployment of agents, refer to 4.1 “Agent deployment options” on page 288.3.1.6 Configuration considerations This 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 environment In this environment, all of the components are installed on one server: DB2 Agent Manager Data server Device server CLI GUI Two server environment In 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 – CLI74 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 order Install the components in the following order: 1. DB2 2. Data Manager 3. TotalStorage Productivity Center components 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.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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 75
  • 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).76 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-2 Computer name6. 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 name7. If you made any changes, you might need to restart your computer (Figure 3-4).Figure 3-4 You must restart Chapter 3. Installing IBM TotalStorage Productivity Center for Data 77
  • 3.2.2 Activate NetBIOS settings If 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).78 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-6 Advanced TCP/IP properties3.2.3 Using and defining user IDs and passwords In 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 fields There are rules for the user IDs and passwords that are used for TotalStorage Productivity Center. For a Typical installation The 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: - _ . Chapter 3. Installing IBM TotalStorage Productivity Center for Data 79
  • Common agent Registration Password or Resource Manager Registration user ID and password 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: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } | ; : " , . < >/? For a Custom installation The 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: – Uppercase characters: A through Z – Lowercase characters: a through z – Numeric characters: 0 through 9 – Non-alphanumeric characters: ~ @ # % ^ & ( ) - _ { } . The WebSphere Application Server user ID and password or Host Authentication password 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: - _ . The Common agent Windows Service user ID or NAS Filer user ID 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: ` ~ # % ^ & ( ) - _ { } . The Common agent Windows Service password or NAS Filer password must contain characters from the following categories: – Uppercase characters: A through Z – Lowercase characters: a through z – Numeric characters: 0 through 980 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • – Non-alphanumeric characters: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } | ; : " , . < >/? The Common agent Registration password or Resource Manager Registration user ID and password 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: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } | ; : " , . < >/?User IDs and passwords created during installationTable 3-2 through Table 3-12 on page 87 contain information about the user IDsand passwords that are used during the installation of the TotalStorageProductivity Center prerequisites and components.Table 3-2 Installing DB2 and Agent Manager Item OS Description Created when Used when Installing All Log on N/A. Used to log on DB2 and Windows as a Windows to Agent local install DB2 and Manager Administrator. Agent Manager. Group User ID Password ITSO’s user ID and password Administrator User ID used to Used to log on. Administrator/ log on. password. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 81
  • Table 3-3 Installing Device server or Data server Item OS Description Created Used when when Installing All Add user ID to DB2 Must be Used to Device Admin group or assign created log on to server or the user rights: before Windows Data server Log on as a starting the to install service. Device server Device Act as part of the and Data server and operating system. server Data Adjust memory installation. server. quotas for a process. Create a token object. Debug programs. Replace a process level token. On Linux or UNIX, give root authority. Group User ID Password ITSO’s user ID and password Administrator New user ID used to New tpcadmin/ log on to Windows. password tpcadmin. used to log on Windows.82 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Table 3-4 Installing Data agent or Fabric agent Item OS Description Created when Used when Installing All User rights: Has to be Used to log on Data agent Act as part of created before to Windows to or Fabric the operating starting the install Data agent system. Data agent or agent or Log on as a Fabric agent Fabric agent. service. installation. On Linux or UNIX, give root authority. Group User ID Password ITSO’s user ID and password Administrator New user ID used New password tpcadmin/ to log on to used to log on tpcadmin. Windows. to Windows.To install a GUI or CLI, you do not need any particular authority or special userID (Table 3-5).Table 3-5 DB2 administration server Item OS Description Created when Used when DB2 All Used to run the Specified when Used by the administration DB2 administration DB2 is DB2 GUI tools server user server on your installed. to perform system. Used by administration the DB2 GUI tools tasks. to perform administration tasks. See the rules in “DB2 user ID and password rules”. Group User ID Password ITSO’s user ID and password New user ID. New password. db2tpc/db2tpc. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 83
  • DB2 user ID and password rules DB2 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.84 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Table 3-6 Certificate authority password Item OS Description Created when Used when Certificate All This password locks Specified when You need to authority the you install Agent specify the value password CARootKeyRing.jks Manager. for the certificate file. Specifying a authority value for this password only if password is you need to optional. You need to specify this open the password only if you truststore files to want to be able to examine the unlock the certificate certificates that authority files. they contain. We recommend that you create a password. group User ID Password ITSO’s user ID and password N/A N/A No default. If not tpctpc. specified, a password is generated automatically. Important: Do not change the agent registration password under any circumstances. Changing this password will render the certificates unusable.Table 3-7 Common agent registration passwords Item OS Description Created when Used when Common All. This is the Specified when Used during agent password you install Common agent, registration required by the Agent Manager. Data agent, and Common agent to Fabric agent register with the installation. Agent Manager. Group User ID Password ITSO’s user ID and password N/A. N/A. changeMe changeMe. (the default). Chapter 3. Installing IBM TotalStorage Productivity Center for Data 85
  • Table 3-8 Common agent service logon user ID and password Item OS Description Created when Used when Common Windows. This creates a new Specified when N/A. agent service account you install Data service under which the agent or Fabric logon user Common agent agent (only ID and runs. local). password Group User ID Password ITSO’s user ID and password Admini- If you do not N/A. tpcadmin/ strators. specify anything, tpcadmin. itcauser is created by default. Table 3-9 Host authentication password Item OS Description Created when Used when Host All. N/A. Specified when Used when you authentication you install the install Fabric agent password Device server. to communicate with the Device server. Group User ID Password ITSO’s user ID and password N/A. N/A. Must be tpctpc. provided. Table 3-10 NAS filer login user ID and password Item OS Description Created when Used when NAS filer login Windows. N/A. Specified N/A. user ID and when you run password NAS discovery. Group User ID Password ITSO’s user ID and password N/A. N/A. N/A. N/A.86 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Table 3-11 Resource manager registration user ID and password Item OS Description Created when Used when Resource All. N/A. Specified when Used when Device manager you install server and Data registration user Device server server have to ID and password and Data register to Agent server. Manager. Group User ID Password ITSO’s user ID and password N/A. manager password manager/ (by default). (by default). password. Table 3-12 WebSphere Application Server administrator user ID and password Item OS Description Created when Used when WebSphere All. You can use Specified Used when Application tpcadmin in when you Device server has Server order to avoid install Device to communicate administrator creating a new server. with WebSphere. user ID and user ID and password password. Group User ID Password ITSO’s user ID and password N/A. If not provided, it if not provided, tpcadmin/ will be created. it will be tpcadmin. created.3.3 Windows installation This section describes the installation of TotalStorage Productivity Center in a Windows environment.3.3.1 DB2 installation for Windows In 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). Chapter 3. Installing IBM TotalStorage Productivity Center for Data 87
  • Note: TotalStorage Productivity Center V3.3 requires DB2 Version 8.1.14 (includes Fix Pack 14) or higher. 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.88 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-8 Select product The InstallShield Wizard starts (Figure 3-9).Figure 3-9 Preparing to install Chapter 3. Installing IBM TotalStorage Productivity Center for Data 89
  • 4. The DB2 Setup wizard window is displayed, as shown in Figure 3-10. Click Next to proceed. Figure 3-10 Setup wizard90 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 91
  • 6. To select the installation type, accept the default of Typical and click Next to continue (Figure 3-12). Figure 3-12 Typical installation92 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 93
  • 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. Note: The default drive for the DB2 installation on the Windows platform is C: and the default path is Program FilesIBMSQLLIB. At this point, you can change the defaults as we did or accept the default configuration. 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.94 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 95
  • 11.In the Configure DB2 instances window, accept the default and click Next to continue (Figure 3-16). Figure 3-16 Configure DB2 instances96 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 97
  • 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 notifications98 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 99
  • 14.The window shown in Figure 3-20 is presented. Click Install to continue. Figure 3-20 Start copying files100 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 101
  • 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.102 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-23 Universal Database First Steps windowVerifying the installation1. To verify the DB2 installation, check if the db2tpc user has been created and included in the DB2ADMNS group. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 103
  • 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.104 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-25 Windows Services showing DB2 services3.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 ..jrewindows Chapter 3. Installing IBM TotalStorage Productivity Center for Data 105
  • Operating system Command Java error failure alternate command 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. 2. The InstallShield Wizard starts, and you see a window similar to the one shown in Figure 3-26. Figure 3-26 InstallShield Wizard window106 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 107
  • 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. Note: The default directory name for Agent Manager is C:Program FilesIBMAgentManager. Figure 3-28 Directory Name window108 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 109
  • 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 FilesIBMSQLLIB. – 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 you110 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 window8. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 111
  • 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 -an112 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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.Figure 3-32 WebSphere Application Server Connection Information window Chapter 3. Installing IBM TotalStorage Productivity Center for Data 113
  • 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 specified114 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 115
  • 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.116 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-36 Define the Certificate Authority window13.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”. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 117
  • – 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. Note: The Agent Manager V1.2 installer provided a default password of changeMe. For Agent Manager 1.3.2, there is no default password. You must provide a password here; otherwise, you cannot continue the installation process. Figure 3-37 Agent Manager Set Passwords window118 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 119
  • 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.120 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 121
  • 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 applications122 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 123
  • 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 AgentManager124 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 125
  • 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 installation You can verify the installation by running the HealthCheck utility from a command prompt. From the command prompt, first navigate to the <InstallDir>IBMAgentManagertoolkitbin directory and run HealthCheck. To understand how to use HealthCheck, refer to the HealthCheck.readme file, which is located in the <InstallDir>IBMAgentManagertoolkit 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.126 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-46 HealthCheck utility resultIn Figure 3-47, verify that the ARS.version field shows the level that you haveinstalled (in our case, it is 1.3.2.26). Confirm that you have received the messageHealth Check passed at the end of the HealthCheck utility listing, as shown inFigure 3-47.Figure 3-47 HealthCheck utility result Chapter 3. Installing IBM TotalStorage Productivity Center for Data 127
  • 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 database128 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Important: For Windows, log on to your system as a local administrator with database authority. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 129
  • 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 select I 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.130 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • – 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 131
  • 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 selection132 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 133
  • 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).134 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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.Figure 3-57 DB2 schema space Chapter 3. Installing IBM TotalStorage Productivity Center for Data 135
  • 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 information136 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 137
  • Verifying the installation To 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 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. Log files Check for errors and Java exceptions in the log files at the following locations: <InstallLocation>TPC.log <InstallLocation>logdbSchemainstalldbSchemaInstallIS.log For Windows, the default InstallLocation is c:Program FilesIBMTPC. Check for the success message at the end of the log files to verify a successful installation.138 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3.3.4 Installing the Data server, Device server, GUI, and CLI In our environment, we performed a custom installation of the Data server, Device server, GUI, and CLI. Preinstallation tasks To 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 installation To 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 139
  • 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 selection140 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 141
  • 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 Administrators142 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 isdisplayed. You can assign a Windows OS group to a role group for eachTotalStorage Productivity Center role with which you want to make anassociation, so we can have multiple authority user IDs to perform variousTotalStorage Productivity Center operations. The operating group must existbefore you can associate a TotalStorage Productivity Center role with a group.You do not have to assign security roles at installation time; you can assignthese roles after you have installed TotalStorage Productivity Center.If you click NAS discovery, the NAS discovery information window isdisplayed. You can enter the NAS filer login default user name and passwordand the SNMP communities to be used for NAS discovery. You do not have toassign the NAS discovery information at installation time; you can configure itafter you have installed TotalStorage Productivity Center. Refer to 4.9.1“Manual NAS/NetWare server entry” on page 345 for details.Click Next to continue. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 143
  • 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).144 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • – 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>IBMAgentManagertoolkitbin directory. Click Next to continue.Figure 3-65 Agent Manager information Chapter 3. Installing IBM TotalStorage Productivity Center for Data 145
  • 10.The Summary information window is displayed. Review the information, and then click Install to continue (Figure 3-66). Figure 3-66 Summary of installation146 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 147
  • 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. 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:tpc33disk1 C:tpc33disk2 Figure 3-68 Multiple disk installation window148 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 149
  • Verifying the installation At 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 server Check the logs for any errors or Java exceptions. The log files for the Data server are: <InstallLocation>TPC.log <InstallLocation>logdatainstall <InstallLocation>loginstall <InstallLocation>datalog For Windows, the default InstallLocation is C:Program FilesIBMTPC. Log files for the Device server Check the log files for any errors. The log files for the Device server are: <InstallLocation>TPC.log <InstallLocation>logdeviceinstall <InstallLocation>devicelog For Windows, the default InstallLocation is c:Program FilesIBMTPC.150 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Log files for GUI Check the log files for any errors. The log files for the GUI are: <InstallLocation>TPC.log <InstallLocation>logguiinstall <InstallLocation>guilog For Windows, the default InstallLocation is c:Program FilesIBMTPC. Log files for CLI Check the log files for any errors. The log files for the CLI are: <InstallLocation>TPC.log <InstallLocation>logcliinstall For Windows, the default InstallLocation is c:Program FilesIBMTPC.3.4 Linux installation This 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 151
  • 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 launchpad152 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 153
  • 3. The DB2 Setup wizard is loaded (see Figure 3-73). Figure 3-73 DB2 Setup wizard: Welcome window154 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 155
  • 5. The Select the installation type window appears (Figure 3-75). Figure 3-75 DB2 Setup wizard: Installation type156 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 157
  • 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).158 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-78 DB2 Setup wizard: DB2 Administration Server user information9. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 159
  • The Set up a DB2 instance window will display (Figure 3-79). Figure 3-79 DB2 Setup wizard: DB2 instance setup160 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 161
  • 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 window162 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 163
  • 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).164 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-84 DB2 Setup wizard: Administration contact list window15.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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 165
  • 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 window166 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 167
  • 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).168 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 installation To 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: db2level exit Chapter 3. Installing IBM TotalStorage Productivity Center for Data 169
  • 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 Pack TotalStorage 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 Pack Complete 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/db2linu xIA32v9/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.tar170 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 7. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command: su - db2inst18. Source the environment by issuing the following command: . ~/sqllib/db2profile9. Type the following commands to shut down the DB2 environment: db2 force applications all db2 terminate db2stop db2licd -end exit10.Switch to the DAS user authority. For example, if your DB2 DAS user is dasusr1, type the following command: su - dasusr111.Type the following commands to source the environment and shut down DB2 DAS: . ~/das/dasprofile db2admin stop exit12.As the root user, issue the following commands to disable the DB2 fault monitor: cd /opt/ibm/db2/V9.1/bin 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. ./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/db2fix1514.Install the Fix Pack by issuing the following command: ./installFixPak -b /opt/ibm/db2/V9.1/ Chapter 3. Installing IBM TotalStorage Productivity Center for Data 171
  • 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=ON export EXTSHM db2set 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: db2start exit 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/dasprofile db2admin start exit172 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Note: Please note that there is a space between . and /home 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 173
  • 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.174 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-90 InstallShield Wizard: Directory Name4. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 175
  • 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 Registry176 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 177
  • 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, and178 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 179
  • 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 Name180 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 181
  • 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 Name182 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 183
  • 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 Summary184 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 185
  • 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 information186 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 187
  • 16.The Agent Manager Application Server will be started immediately, as shown in Figure 3-103. Figure 3-103 InstallShield Wizard progress188 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 189
  • 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 summary3.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 group Before 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.190 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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.Follow these steps to add the root user to the instance group, which, in ourinstallation, 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 ~]# groups root 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 191
  • 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/group db2grp1:x:102:root Now, your system is ready for you to install the TotalStorage Productivity Center components. Install the database schema If 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 window192 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 193
  • 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 installation194 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 195
  • 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 administrator196 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 information7. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 197
  • Select System managed (SMS), click OK, and click Next to proceed. Figure 3-112 TotalStorage Productivity Center Installer: Database schema creation198 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 199
  • 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.200 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-115 TotalStorage Productivity Center Installer: Installation summary3.4.6 Install TPC V3.3 Data server, Device server, CLI, and GUI Follow 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 201
  • 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 agreement202 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 203
  • 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 installation204 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 205
  • 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.206 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 207
  • 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 Mapping208 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 209
  • 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 Click Next to continue.210 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 211
  • 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 selection212 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 213
  • 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.214 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 CD If 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 image To 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 215
  • 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 display This 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 installation Follow these steps to perform the installation of IBM DB2 UDB: 1. At the command prompt on the host, type the following command: ./db2setup216 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • The DB2 setup launchpad opens (Figure 3-131).Figure 3-131 DB2 Setup launchpad Chapter 3. Installing IBM TotalStorage Productivity Center for Data 217
  • 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 selection218 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 219
  • 4. Click Next. The Software License Agreement window appears (Figure 3-134). Figure 3-134 DB2 Software License Agreement220 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 221
  • 6. Select Typical and then click Next. The Select the installation action window appears (Figure 3-136). Figure 3-136 DB2 installation action222 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 223
  • 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 information224 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 225
  • 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 partitioning226 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 227
  • 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 user228 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 229
  • 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 notifications230 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 231
  • 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).232 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-147 DB2 installation progress18.When DB2 has been successfully installed, an installation summary window appears (Figure 3-148).Figure 3-148 DB2 post-installation steps Chapter 3. Installing IBM TotalStorage Productivity Center for Data 233
  • 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 installation To 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: db2level exit234 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 server If 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 Pack TotalStorage 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 Pack Complete 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 235
  • 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/db2aix5 v9/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 all db2 terminate db2stop db2licd -end $HOME/sqllib/bin/ipclean exit 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/dasprofile db2admin stop exit 11.As the root user, issue the following commands to unload shared libraries and disable the DB2 fault monitor: /usr/sbin/slibclean cd /opt/IBM/db2/V9.1/bin236 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. ./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.s06110813.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 db2inst115.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 dasusr116.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/sqllib17.Then, edit the userprofile contained in that directory. Add the following lines to the file and then save the file: EXTSHM=ON export EXTSHM db2set DB2ENVLIST=EXTSHM18.Next, you must restart DB2. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command: su - db2inst1 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 237
  • 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: db2start exit 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/dasprofile db2admin start exit Add the root user to the DB2 instance group You 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).238 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3.5.4 Agent Manager installation for AIX After 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 CD If 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. 2. Insert the CD into the CD-ROM or DVD-ROM drive on your system. 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: mount -o ro /dev/cd0 /cdrom 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 image To 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 239
  • 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. 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. 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 display This 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 installation Follow 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).240 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 241
  • 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.242 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 243
  • 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 information244 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 245
  • 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.246 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Click Next to continue.Figure 3-155 InstallShield Wizard: WebSphere Application Server connection information Chapter 3. Installing IBM TotalStorage Productivity Center for Data 247
  • 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 information248 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 249
  • 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 Authority250 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 251
  • 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 Summary252 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 253
  • 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 AgentManager254 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 255
  • 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 server If 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.256 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3.5.5 Install TotalStorage Productivity Center V3.3 database schema After 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 components After 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 CD If 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. 2. Insert the CD into the CD-ROM or DVD-ROM drive on your system. 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: mount -o ro /dev/cd0 /cdrom 5. Change to the newly mounted filesystem, for example: cd /cdrom Proceed to “Preparing the display” on page 240. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 257
  • Accessing the installation media using a downloaded image To 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. 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. 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 environment If 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 Note: You must install TotalStorage Productivity Center as the root user. However, you must still source the environment using the instance owner. Assigning filesystem ownership If 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 /dbtemp258 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Installing the database schemaWe consider it a best practice to split the installation of TotalStorage ProductivityCenter 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 forTotalStorage Productivity Center:1. At the command prompt on the DB2 host, type the following command: ./setup.sh2. 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 259
  • 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 agreement260 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 261
  • 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 selection262 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 263
  • 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).264 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-171 TotalStorage Productivity Center database schema details9. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 265
  • 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 summary266 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 10.Click Install to begin the database schema installation. A progress window appears (Figure 3-173).Figure 3-173 TotalStorage Productivity Center installation progress Chapter 3. Installing IBM TotalStorage Productivity Center for Data 267
  • 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 GUI After 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).268 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-175 TotalStorage Productivity Center installation language selection3. 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 269
  • 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 types270 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 271
  • 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).272 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-180 Data server database schema information8. 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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 273
  • 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).274 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 3-182 Data server security roles mapping11.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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 275
  • 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.276 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • When you have finished making your selections, click Next. The Agent Manager information window appears (Figure 3-184).Figure 3-184 Agent Manager information14.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. Chapter 3. Installing IBM TotalStorage Productivity Center for Data 277
  • The summary information window appears (Figure 3-185). Figure 3-185 Data server installation summary278 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 15.Click Install. The Data server installation begins. A progress window appears (Figure 3-186).Figure 3-186 Data server installation progress Chapter 3. Installing IBM TotalStorage Productivity Center for Data 279
  • 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. 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 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.280 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3.6.1 Launch the TotalStorage Productivity Center GUI Start 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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 281
  • 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. Click282 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 windowAt this point, the Java applet for the TotalStorage Productivity Center GUI willdownload. The applet jarfile can take a while to load into your browser the firsttime. Be patient, because there is no progress bar displayed to indicate whatprogress is being made. After the applet jarfile has been loaded into yourbrowser, it will remain in your browser cache until you dump it. Subsequent startsof the TotalStorage Productivity Center GUI load much faster.After the applet has loaded, it launches the TotalStorage Productivity CenterGUI. In the center of the GUI, the Sign-on window appears. It is prefilled with theServer address and access port (9549 for TotalStorage Productivity CenterV3.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 Chapter 3. Installing IBM TotalStorage Productivity Center for Data 283
  • 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 GUI3.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 FilesIBMTPCcasubagentsTPCData – For AIX and Linux: /opt/IBM/TPC/ca/subagents/TPC/Data/284 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3. Edit the agent.config file in: – For Windows: C:Program FilesIBMTPCcasubagentsTPCDataconfig – 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 configuration4. 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 FilesIBMca’”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 3. Installing IBM TotalStorage Productivity Center for Data 285
  • 286 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 4 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.© Copyright IBM Corp. 2009. All rights reserved. 287
  • 4.1 Agent deployment options TotalStorage 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 installation Local 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 installation Remote 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.288 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 agents Before 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 password4.2.1 Interactive installation Start 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. The290 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • default is C:Program FilesIBMTPC 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 FilesTivoli 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 291
  • 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.292 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • – 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. 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.8. Next, select options for the Data agent, as shown in Figure 4-5.Figure 4-5 Local interactive installation: Server and agent settings9. 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 293
  • – 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. 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. 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.294 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. 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.Figure 4-7 Local interactive installation: Tivoli Agent Manager information Click Next to continue. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 295
  • 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 FilesIBMTPCca 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.296 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-9 Common agent service name and user information15.Enter the information and click OK, which will bring you back to the window shown in Figure 4-8 on page 296. Click Next. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 297
  • 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).298 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 299
  • 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) installation For 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,300 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • # 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 optionstates# 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 optionstates# are stored as Variables and must be set with -V#-V LICENSE_REJECT_BUTTON=”false”######################################################################### IBM TotalStorage Productivity Center Install Location Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 301
  • # # 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 FilesMy # Product, use # # -P installLocation="C:Program FilesMy Product" # -P installLocation="C:Program FilesIBMTPC" ####################################################################### ####################################################################### # 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"302 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • ######################################################################### 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 303
  • -V varCAPort="9510" ####################################################################### # # # Common Agent Registration Password -V varCAPassword="changeMe" ####################################################################### # # # CA Installation Location -V varCAInstallLoc="C:Program FilesIBMTPCca" ####################################################################### # # # 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" #######################################################################304 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • ### 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 305
  • # #-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,306 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 installation Before 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 307
  • 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/sshd4.3.2 Performing the remote installation The 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.308 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-13 Remote installation: Language selection2. 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 Click Next to continue. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 309
  • 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 location310 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 311
  • 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 settings312 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 313
  • 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. 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. 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.314 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-20 Remote Installation: List of remote computers to install the Data agent 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.10.When you are satisfied with your list of target computers, click Next. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 315
  • 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.316 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-22 Remote installation: Ready to install13.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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 317
  • 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. 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: You can review the Installation log for each computer by double-clicking the computer name or the IP address.318 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-24 Remote installation: Installation complete16.Click Done to continue (Figure 4-25).Figure 4-25 Remote installation: Installation summaryThe 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 Fabricagents (if you choose to install them), because they now run a Common agent. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 319
  • 4.4 Verifying the installation After 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 installation320 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • The install process creates a directory structure on the servers, which is similarto the directory structure shown in Figure 4-27 for a Windows server. For UNIXand Linux systems, the tree is created under /opt/IBM/ by default and otherwiselooks the same.Figure 4-27 Directory tree for Data and Fabric agent installation Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 321
  • 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 installation322 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 4.4.1 Log files The 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. Note: The default <InstallLocation> differs in local and remote administration. Data agent logs The following installation logs are for the Data agent when installed locally: <InstallLocation>logsubagentsTPCDatainstall 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>logsinstall <InstallLocation>subagentsTPCDatalog The following installation logs are for the Data agent when installed remotely for UNIX and Linux: <InstallLocation>/logs/ <InstallLocation>/subagents/TPC/Data/log/ <InstallLocation>/logs/ The following operational log is for the Data agent when installed locally for Windows: <InstallLocation>casubagentsTPCDatalog<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>/ Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 323
  • The following operational logs are for the Data agent when installed remotely for Windows: <InstallLocation>logs <InstallLocation>subagentsTPCDatalog<host name> The following operational logs are for the Data agent when installed remotely for UNIX and Linux: <InstallLocation>/logs/ <InstallLocation>/subagents/TPC/Data/log/<host name> Common agent logs The following installation and operational logs are for the Common agent when installed locally for Windows: <InstallLocation>calogs <InstallLocation>calogsinstall 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 <InstallLocation>logsinstall The following installation and operational logs are for the Common agent when installed remotely for UNIX and Linux: <InstallLocation>/logs/ <InstallLocation>/logs/install/4.5 Uninstalling the Data agent For 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).324 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 uninstallation You 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 325
  • 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.4.5.2 Local uninstallation If 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.326 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 selection4. Click OK to continue. You see the TotalStorage Productivity Center Installer Welcome window (Figure 4-33).Figure 4-33 Local agent uninstall: Welcome window Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 327
  • 5. Click Next to continue. 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 6. Click Next to continue. You see a summary of the components that TotalStorage Productivity Center Installer is about to uninstall (Figure 4-35 on page 329).328 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-35 Local agent uninstall: Summary window Click Next to continue. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 329
  • 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 complete4.5.3 Remote agent uninstallation If 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.330 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 deployedagents Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 331
  • 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.332 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 deployedagents Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 333
  • 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.334 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-41 Local agent uninstall: Uninstall of remotely deployed Data agent7. 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 completed8. Click OK, and restart your system. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 335
  • 4.6 Upgrading the Data agent The 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 FileIBMTPCdataupgrade. 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.336 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • The tree structure is similar to Figure 4-43.Figure 4-43 Copy the upgrade.zip file to the server upgrade directories Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 337
  • 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.338 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 339
  • 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.340 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 341
  • Figure 4-47 Configuration the Alert Disposition 3. Save to make the changes permanent.4.8 Log file retention You 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.342 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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.Figure 4-48 Log-File Retention4.8.1 Quota and constraint e-mail address rules If 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 343
  • 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. Save to make the changes permanent.4.9 Scan/probe agent administration You 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.344 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 3. The Filesystem Agent Editor window appears. Click the scan/probe agent drop-down list and assign an agent to a selected volume. 4. Save to make the changes permanent.4.9.1 Manual NAS/NetWare server entry You 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 345
  • 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.346 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 SettingsAll UsersApplication DataVMwareVMware VirtualCenterSSL 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.* Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 347
  • 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.348 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 349
  • 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.350 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-54 Add VMware VI Data Source6. 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 status7. 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 351
  • 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.352 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 aggregator History 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”. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 353
  • 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.354 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Note: You must have previously defined SNMP, Tivoli Event Console, or an e-mail server in order for the alert to successfully run. 5. Save to make the changes permanent by pressing Ctrl+s.4.11.1 Data Manager NetWare tree logins The 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 355
  • 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 logins Data 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 CIMOMs There 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).356 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 job In 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 357
  • 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.358 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 359
  • 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. 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 job Follow 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.360 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 361
  • 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 can362 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 363
  • User IDs and passwords Now, 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.364 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 365
  • Manually entering CIMOMs Next, 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).366 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-70 Configuring CIMOMs: CIMOM configuration is complete 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.We have now completed the configuration of our CIMOMs in the TotalStorageProductivity Center. However, the retrieval of the information about the managedelements (storage subsystems, tape library, and switch) has not yet occurred forthose CIMOMs that require authentication. So, we have to run a further CIMOMdiscovery 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 theconfigured CIMOMs and retrieve all information about the managed storagesubsystems, tape libraries, and switches. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 367
  • 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 Logs We 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.368 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 retention You 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 5. Save to make the changes permanent. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 369
  • 4.13.1 Removed resource retention This 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. 3. Save to make the changes permanent.370 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 4.13.2 Resource history retention for databases You 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 5. Save to make the changes permanent. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 371
  • 4.13.3 Removed resource retention for databases This 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 3. Save to make the changes permanent.4.13.4 Adding databases In 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.372 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 373
  • • 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.374 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 4.13.5 Configuring chargeback If 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. Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 375
  • – 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.376 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 4-81 Chargeback sample invoice Chapter 4. Configuring IBM TotalStorage Productivity Center for Data 377
  • Figure 4-82 Chargeback CIMS format378 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 5 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.© Copyright IBM Corp. 2009. All rights reserved. 379
  • 5.1 Operations The 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 interface The 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 Tree The 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.380 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 5-1 TotalStorage Productivity Center Navigation TreeThe primary groups of the Navigation Tree relating to TotalStorage ProductivityCenter 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 ChargebackEach 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 pane The 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).382 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • Figure 5-2 Content pane: Data agent example5.1.2 Administrative services You 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. 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. Figure 5-3 Administrative services Chapter 5. Operations and reporting 383
  • Services When 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 server Under 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 required384 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 Chapter 5. Operations and reporting 385
  • 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 FilesIBMTPCDatalogserver_xxxxxx.log – For the Scheduler component: C:Program FilesIBMTPCDatalogScheduler_xxxxxx.log – For CIMOM component: C:Program FilesIBMTPCDatalogcimom_xxxxxx.log – For the agent component: C:Program FilesIBMTPCDatalogTPCD_xxxxxx.log Figure 5-8 on page 387 shows a sample Scheduler log display in the content pane.386 Deployment Guide Series: IBM TotalStorage Productivity Center for Data
  • 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 FilesIBMTPCDatalogServerTrace.log Chapter 5. Operations and reporting 387
  • 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. 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. 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.388 Deployment Guide Series: IBM TotalStorage Productivity Center for Data