Beruflich Dokumente
Kultur Dokumente
ibm.com/redbooks
International Technical Support Organization Deployment Guide Series: IBM TotalStorage Productivity Center for Data June 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 ADP Schedule 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
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
iv
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 . . . . . . . . . 139 3.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 . . . . . . 201 3.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 . . . . . . 268 3.6 GUI for Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 3.6.1 Launch the TotalStorage Productivity Center GUI . . . . . . . . . . . . . 281 3.7 Changing the agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Chapter 4. Configuring IBM TotalStorage Productivity Center for Data. 287 4.1 Agent deployment options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 4.1.1 Local installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 4.1.2 Remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 4.2 Local installation of Data and Fabric agents . . . . . . . . . . . . . . . . . . . . . . 289 4.2.1 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 4.2.2 Unattended (silent) installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 4.3 Remote installation of Data agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 4.3.1 Preparing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . 307 4.3.2 Performing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . 308 4.4 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 4.4.1 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 4.5 Uninstalling the Data agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 4.5.1 Remote uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 4.5.2 Local uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 4.5.3 Remote agent uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 4.6 Upgrading the Data agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 4.7 Alert disposition (SNMP and e-mail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 4.8 Log file retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 4.8.1 Quota and constraint e-mail address rules . . . . . . . . . . . . . . . . . . . 343 4.9 Scan/probe agent administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 4.9.1 Manual NAS/NetWare server entry . . . . . . . . . . . . . . . . . . . . . . . . . 345
Contents
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
vi
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 523 5.8 VMware ESX Server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 5.8.1 Topology Viewer for VMware Environment . . . . . . . . . . . . . . . . . . . 531 5.8.2 Reports for VMware Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 535 5.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Appendix A. Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565 User IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Server information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Worksheet for user IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 567 User IDs and passwords for key files and installation . . . . . . . . . . . . . . . . 568 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 TotalStorage Productivity Center documentation . . . . . . . . . . . . . . . . . . . . . . 571 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Contents
vii
viii
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
ix
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX 5L AIX BladeCenter DB2 Universal Database DB2 DS4000 DS6000 DS8000 Enterprise Storage Server FlashCopy GPFS HACMP IBM NetView POWER5 POWER6 POWER Redbooks Redbooks (logo) System i System p System Storage System x System z Tivoli Enterprise Console Tivoli TotalStorage WebSphere z/OS
The following terms are trademarks of other companies: Network Appliance, WAFL, FlexVol, Data ONTAP, NetApp, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and other countries. Novell, SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and other countries. Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its affiliates. QLogic, and the QLogic logo are registered trademarks of QLogic Corporation. SANblade is a registered trademark in the United States. Red Hat, and the Shadowman logo are trademarks or registered trademarks of Red Hat, Inc. in the U.S. and other countries. VMware, the VMware "boxes" logo and design are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Java, JDBC, JRE, JVM, Solaris, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Active Directory, Internet Explorer, Microsoft, MS, SQL Server, Windows NT, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
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.
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.
The authors of the previous version of this book are Sanver Ceylan, Hartmut Harder, and Murat Hakan Yesilmen.
xii
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 Specialist
Comments 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
Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
xiv
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.
New information
TotalStorage Productivity Center for Data V3.3 product enhancements documented How to maintain your TPC for Data repository data and agents
xv
xvi
Chapter 1.
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.
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.
The Data server is the control point for product scheduling functions, configuration, event information, reporting, and GUI support. It coordinates communication with agents and data collection from agents that scan filesystems and databases to gather storage demographics and populate the database with results. Automated actions can be defined to perform filesystem extension, data deletion, and Tivoli Storage Manager backup, archiving, or event reporting when defined thresholds are encountered. The Data server is the primary contact point for GUI user interface functions. It also includes functions that schedule data collection and discovery for the Device server. The Device server component discovers, gathers information from, analyzes the performance of, and controls storage subsystems and SAN fabrics. It coordinates communication with agents and data collection from agents that scan SAN fabrics. The single database instance serves as the repository for all TotalStorage Productivity Center components.
The Data agents and Fabric agents gather host, application, and SAN fabric information and send this information to the Data server or Device server. The graphical user interface (GUI) allows you to enter information or receive information for all TotalStorage Productivity Center components. The command-line interface (CLI) allows you to issue commands for major TotalStorage Productivity Center functions.
Monitors storage assets that are associated with enterprise-wide databases and issues notifications of potential problems Provides a wide variety of standardized reports about filesystems, databases, and storage infrastructure to track usage and availability Provides file analysis across platforms to help you to characterize your data and, in turn, identify and reclaim space used by non-essential files Provides policy-based management and automated capacity provisioning for filesystems when user-defined thresholds are reached or a condition is met Generates invoices that charge back for storage usage on a departmental, group, or user level These functions that are available with Data Manager are designed to help decrease storage costs by: Improving storage utilization Enabling intelligent capacity planning Supporting application availability through computer uptime reporting and application database monitoring Provide automation for invoking backups, archiving, scripts, publishing reports to Web servers, and so on The architecture of TotalStorage Productivity Center for Data enables system administrators to see all of the storage assets, including direct-attached storage and network-attached storage. This comprehensive view of the entire storage map allows the administrators to manage much larger environments and also to get the information about utilization and usage that is typically required in large environments. The information collected by TotalStorage Productivity Center for Data can help you make intelligent decisions about optimizing the utilization of your open system environments. The data collected by TotalStorage Productivity Center for Data helps you to understand what is happening to the data that resides on your servers. The collected data includes views illustrating when files are created, accessed, and modified, and by which group or user. This type of information enables system administrators to map the actual storage resource to the consumers of that resource. The ability to map storage consumption to storage hardware has become increasingly important as the size of open systems environments has increased. In addition to understanding the current consumption and usage of data within the enterprise, TotalStorage Productivity Center for Data keeps track of this information over time. Not only does this historical view of storage consumption and utilization allow you to see usage trends over time, it also enables the system administrator to see a projected use of storage into the future. This capability allows the system administrator to plan
the purchase of additional capacity in a planned, proactive manner rather than just react to your system running out of space. The major components of TotalStorage Productivity Center for Data are: Data Manager The Data Manager controls the discovery, monitoring, reporting, and alert functions. Data Manager: Receives information from the agents and stores that information in the central repository and issues commands to agents for jobs Receives requests from clients for information and retrieves the requested information from the central data repository Data Manager can help you identify, evaluate, control, and predict your enterprise storage management assets. Because it is policy-based, it can detect potential problems and automatically make adjustments based on the policies and actions that have been created. For example, it can notify you when your system is running out of disk space or warn you of storage hardware failure. By alerting you to these and other issues related to your stored data, it gives you an opportunity to prevent unnecessary system and application downtime. Data agents on managed systems An agent resides on each managed system. Each agent performs the following functions: Runs probes and scans Collects storage-related information about the volumes or filesystems that are accessible to the managed systems Forwards information to the manager to be stored in the database repository Web server The optional Web server permits remote Web access to the server. Clients Clients communicate directly to Data Manager to perform administration, monitoring, and reporting. A client can be a locally installed interface to Data Manager, or it can use the Web server to access the user interface through a Web browser.
1.3 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.
10
Subsystem reporting
TotalStorage Productivity Center for Data gathers and reports on disk subsystems. The information includes physical characteristics, such as the drives manufacturer, model, serial number, capacity, and rotational speed. Also, the information includes how that drives storage is allocated to logical volumes, snapshot copy volumes, and free space. This feature allows users to perform the following tasks (subject to the vendors implementation of Storage Management Initiative Specification (SMIS)): Display the physical disks behind what the host sees as a disk drive Show the allocated and free capacity of subsystems in the network List subsystem volumes that have been allocated but are not in use Show which hosts have access to a given subsystem volume Show which hosts have access to a given disk drive (within the subsystem) Show which subsystem volumes (and disks) a host can access Obtain SAN Volume Controller (SVC) reporting
Topology Viewer
The IBM TotalStorage Productivity Center Topology Viewer is designed to provide an extended graphical topology representation of the physical and logical resources (for example, computers, fabrics, and storage subsystems) in your storage environment. In addition, the Topology Viewer depicts the relationships among resources (for example, the disks comprising a particular storage subsystem). Detailed, tabular information (for example, attributes of a disk) is also provided.
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
Advanced provisioning
TotalStorage Productivity Center and Tivoli Provisioning Manager Workflow automation can reduce provisioning time from hours to minutes and significantly simplify the task of provisioning new storage capacity. This automation is especially valuable when adding storage provisioning to existing automated server provisioning tasks, such as deploying operating systems, software, and network resources.
Comprehensive reporting
With a wide variety of predefined reports, from summaries to detailed reports on storage assets, you can optimize storage, minimize downtime, and streamline storage management.
Database support
TotalStorage Productivity Center for Data manages the storage assets within your database application allowing you to identify the fastest growing databases, spot potential trouble areas, reclaim unused space, and predict future storage needs.
Chargeback support
TotalStorage Productivity Center for Data offers an end-to-end system for invoicing your cost centers based on their storage usage. TotalStorage Productivity Center for Data makes your data owners aware of and accountable for their data usage, helping to keep storage costs distributed accurately across an organization.
13
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.
14
For more information about IBM Tivoli Monitoring and Tivoli Enterprise Portal, go to the following address: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc==/ com.ibm.itm.doc/toc,.xml
Launch-in-context feature
The launch-in-context feature can be used to download the latest version of the TotalStorage Productivity Center graphical user interface (GUI) on the local workstation using Java Web Start. The TotalStorage Productivity Center GUI must have been previously installed on the local workstation. The launch-in-context feature downloads the latest version of the GUI on the local workstation if an older version has been downloaded, or if the IBM TotalStorage Productivity Center GUI has not been previously downloaded. If the latest version exists on the local workstation at the Java Web Start download location, the TotalStorage Productivity Center GUI is not downloaded. The launch-in-context feature can be run in the following ways: 1. From a URL with Java Web Start. You can remotely download and launch the TotalStorage Productivity Center GUI, using the launch-in-context feature, and perform a certain number of actions on a remote system.
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
16
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
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.
17
Figure 1-3 illustrates the architectural overview for TotalStorage Productivity Center for Data.
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
The Managed Resources section on the right side of Figure 1-3 on page 18 illustrates machines that are running the TotalStorage Productivity Center for Data agent component. These machines are the systems from which the TotalStorage Productivity Center server gathers its information, which needs to be done on a regular and scheduled basis in order to keep the information in the repository as current as possible. The architectural diagram in Figure 1-3 on page 18 provides a logical overview of the main conceptual elements and relationships in the architecture, components, connections, users, and external systems. The diagram also shows the various methods that are used to collect information from multiple systems to give an administrator the necessary views of the environment, for example: Software clients (agents) Standard interfaces and protocols (for example, Simple Network Management Protocol) Common Information Model Object Manager (CIMOM agent) Repository Agent Manager with its registry repository
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.
20
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.
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 servers 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
Has an installed NetWare Client. Has access to the Novell NetWare servers and volumes within your environment. For NAS support, install and license an agent on Windows or UNIX machines from which the NAS filers that you want to scan are visible. For example, install agents to Windows machines that can access your NAS filers, and install agents on UNIX/Linux machines that have imports for the filesystems within the NAS filers. See 4.9.1, Manual NAS/NetWare server entry on page 345 for more information. For Microsoft Cluster Server (MSCS) support, install and license an agent on every cluster node machine.
IBM Storage Resource Manager Server Server
Data Repository
JDBC
Scheduler
TCP/IP
SLP
Agents
CM Agent
Disk CIM/OM
Storage Host
TCP/IP
Proxy Agents
Application Server
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 Managers 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 Managers SNMP trap alert notification capabilities, an SNMP Management Information Base (SNMP MIB) is included in the server installation.
24
The SNMP MIB can be found in the file in the default Data Manager installation directory: For Windows: \Program Files\IBM\TPC\Data\snmp\tivoliSRM.mib For UNIX or Linux: opt/IBM/TPC/Data/snmp/tivoliSRM.MIB The MIB is provided for use by your SNMP management console software (for example, IBM Tivoli NetView or Hewlett-Packard (HP) Openview). This MIB allows you to better view Data Manager-generated SNMP traps from within your management console software. For sending SNMP traps, there must be an SNMP service installed and running on the Data Manager server. To check if there is an installed and running SNMP service, do these steps: For Windows: a. Right-click My Computer. b. Click Manage. c. Click Services. For UNIX or Linux: a. For information about whether SNMP is running and if so, on which port, check in /etc/services. The default community name used by Data Manager to forward SNMP traps is
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.
26
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 Server
Resource Manager
Data Server
Resource Manager
Agent Manager
IBMCDB
Holds the registration of all agents and resource managers
Registration Service
Recovery Services
Application Server
Common Agent
Data Agent Fabric Agent
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
29
30
31
32
Chapter 2.
33
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
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
35
Yes with AIX 5100-05 maintenance level Yes in 32-bit compatibility mode with AIX 5100-05 maintenance level Yes with AIX 5100-05 maintenance level Yes in 32-bit compatibility mode with AIX 5100-05 maintenance level Yes with AIX 5200-02 maintenance level Yes in 32-bit compatibility mode with AIX 5200-02 maintenance level Yes with AIX 5300-01 maintenance level and APAR IY70336
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Yes
Yes
36
Platforms
Data server, Device server, database schema, and command-line interface (CLI) Yes in 32-bit compatibility mode with AIX 5300-01 maintenance level and APAR IY70336 Yes Yes in 32-bit compatibility mode No No No
GUI
Yes in 32-bit compatibility mode with AIX 5300-01 maintenance level and APAR IY70336 Yes Yes in 32-bit compatibility mode Yes Yes Yes (agent must run in global zone; non-global or local zone is not supported.) Data agent, Fabric agent on HP-UX 11i Yes Yes Yes Yes Yes Yes
Yes
IBM AIX V6.1 (32-bit) IBM AIX V6.1 (64-bit) Solaris 8 Solaris 9 Solaris 10
Yes Yes No No No
No
No
No
HP-UX 11 and 11i.2 Windows 2000 Advanced Server Windows 2000 Datacenter Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition Red Hat Enterprise Linux AS Version 3.0 on System x
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
37
Platforms
Data server, Device server, database schema, and command-line interface (CLI) No
GUI
Red Hat Enterprise Linux AS Version 3.0 on System p on POWER5 Red Hat Enterprise Linux AS Version 3.0 on System i on POWER 5 Red Hat Enterprise Linux AS Version 4.0 on System x United Linux 1.0 on System x United Linux 1.0 on System z SUSE LINUX Enterprise Server 8, System p on POWER, 4, and System x SUSE LINUX Enterprise Server 9, System x, System p on POWER 5, System i on POWER 5, and System z Supported Guest O.S. on VMware ESX Environment
Data agent
No
No
No
Data agent
No
No
Yes
Yes
Yes
Yes
No No No
No No No
No
Data agent runs on all series; Fabric agent runs on System x only.
No
Yes
No
Data agent
No
Yes
38
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 filers 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.
40
SUSE Linux Enterprise Server 8 and 9 with the following service packs:
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.
42
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.
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
43
44
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.
46
If you have data that you want to migrate from IBM TotalStorage Productivity Center V2.x to V3.x, you can run the Data Migration Utility after you install TotalStorage Productivity Center. A new Migration Utility is available. When you migrate data to IBM TotalStorage Productivity Center Version 3.3, follow the instructions in Chapter 5 in the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774. For additional information about the Data Migration Utility, refer to the IBM TotalStorage Productivity Center Flash at this Web site: http://www.ibm.com/servers/storage/support/software/tpc
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
47
48
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.
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
49
Component Agent Manager - secure SSL Registering agents Registering resource manager Agent Manager - secure SSL with client authentication Providing configuration updates Renewing and revoking certificates Querying the registry for agent information Requesting ID resets Agent Manager Requesting updates to the certificate revocation list Requesting Agent Manager information Downloading the truststore file Alternate port for the Agent Recovery Service Common agent (No access needed) Common agent (No access needed) Common Information Model Object Manager (CIMOM) HTTP CIMOM HTTPS Agent Recovery Service
Server perspective Session Initiator=No Inbound Session Initiator=Yes Inbound and Outbound
Agent perspective Session Initiator=Yes Outbound Session Initiator=No Inbound and Outbound
9512
9513
N/A N/A N/A N/A Session Initiator=No Inbound Session Initiator=Yes Outbound Session Initiator=Yes Outbound Session Initiator=Yes Outbound
Local to Server Local to Server N/A N/A Unsecured connection for Agent Recovery Service action Session Initiator=No Inbound and Outbound Session Initiator=No Inbound and Outbound Session Initiator=No Inbound and Outbound
Push UNIX
SSH(22)
Push Windows
Push UNIX
50
Server perspective Session Initiator=Yes Outbound Session Initiator=Yes Inbound Session Initiator=Yes Inbound Session Initiator=Yes Inbound N/A N/A
Agent perspective Session Initiator=No Inbound and Outbound N/A Session Initiator=No Inbound and Outbound N/A N/A N/A
601 High ports 3000+ TPC for Data server 2078 162 427
Push All Simple Network Management Protocol (SNMP) Listener Port Service Location Protocol (SLP)
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.
52
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
53
54
IBM TotalStorage SAN Filesystem V2.1 and V2.2 from AIX 5L V5.1 (32-bit), Windows 2000 Server and Windows 2000 Advanced Server, Red Hat Enterprise Linux 3.0 Advanced Server, and SUN Solaris 9 clients General Parallel Filesystem (GPFS) V2.1 and V2.2
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
55
56
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.
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 users 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.
58
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.
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
59
60
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.
Agent Manager
IBM WebSphere Application Server V5 Tivoli Agent Manager IBM Tivoli Common agent - C:\Program Files\IBM\TPC\ca IBM TotalStorage Productivity Center - Data server IBM WebSphere Application Server V5 Fabric Manager
LocalSystem
Common agent
itcauser
TSRMsrv1
N/A.
LocalSystem
N/A.
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
61
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
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=ssg1S1003285
Chapter 2. Planning for deployment of IBM TotalStorage Productivity Center for Data
63
64
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.
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.
66
Important: When providers release new versions of their products, these values can change. Check the providers documentation for that providers interop namespace.
Table 2-4 Interoperability namespace summary Vendor Cisco Interoperability namespace /root/cimv2. For version 3.2.1 or later: /root/pg_interop. /interop or /root/brocade1. Note: Contact your switch vendor for the correct namespace to use. /interop. /root/ibm. /interop. /root/emc. 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. /root. /root/sun3510 or /interop. Note: This is for a subsystem and not a switch. /root/ibm. /root/PG_interop.
Brocade
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
Chapter 3.
69
70
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 of agents Retain most recent only Average Rows 100 1000 10000 55 Mb 96 Mb 511 Mb Max. Rows 70 Mb 246 Mb 2009 Mb Retain for seven days Average Rows 69 Mb 240 Mb 1951 Mb Max. Rows 91 Mb 455 Mb 4102 Mb Retain for 14 days Average Rows 86 Mb 408 Mb 3631 Mb Max. Rows 115 Mb 699 Mb 6543 Mb
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 applications port definitions or specifying other port numbers for Agent Manager. The ports that need to be reserved are: 50000 9511 9512 9513 9550 DB2 port Registration port Secure port Public port HTTP server port (GUI Web port)
You have to use a user ID with the appropriate authority: For Windows, you must have administrative authority. For UNIX or Linux, you must have root authority. If the registry data will be in DB2 (local or remote), be sure that DB2 has already been installed. If it is not, the Agent Manager installation program will request that you point to the DB2 installation image in order to install DB2 before creating a registry entry in the database. The default installation directory is: For Windows: c:\Program Files\IBM\... For UNIX or Linux: /opt/IBM/... You can change this path during the installation setup. There are two types of installation of TotalStorage Productivity Center V3.3: typical and custom.
72
73
For information about the deployment of agents, refer to 4.1 Agent deployment options on page 288.
74
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.
5. Enter the host name in the Computer name field. Click More to continue (Figure 3-2 on page 77).
76
6. In the next window, verify that the Primary DNS suffix of this computer field displays a domain name. Click OK (Figure 3-3).
7. If you made any changes, you might need to restart your computer (Figure 3-4).
77
2. Then, select the WINS tab, select Enable NetBIOS over TCP/IP, and click OK (Figure 3-6 on page 79).
78
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: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < >/?
80
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: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < >/?
Group Administrator
81
Table 3-3 Installing Device server or Data server Item Installing Device server or Data server OS All Description Add user ID to DB2 Admin group or assign the user rights: Log on as a service. Act as part of the operating system. Adjust memory quotas for a process. Create a token object. Debug programs. Replace a process level token. On Linux or UNIX, give root authority. User ID Created when Must be created before starting the Device server and Data server installation. Used when Used to log on to Windows to install Device server and Data server.
Group
Password
Administrator
82
Table 3-4 Installing Data agent or Fabric agent Item Installing Data agent or Fabric agent OS All Description User rights: Act as part of the operating system. Log on as a service. On Linux or UNIX, give root authority. User ID Created when Has to be created before starting the Data agent or Fabric agent installation. Used when Used to log on to Windows to install Data agent or Fabric agent.
Group
Password
Administrator
To install a GUI or CLI, you do not need any particular authority or special user ID (Table 3-5).
Table 3-5 DB2 administration server Item DB2 administration server user OS All Description Used to run the DB2 administration server on your system. Used by the DB2 GUI tools to perform administration tasks. See the rules in DB2 user ID and password rules. User ID New user ID. Created when Specified when DB2 is installed. Used when Used by the DB2 GUI tools to perform administration tasks.
Group
83
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
Table 3-6 Certificate authority password Item Certificate authority password OS All Description This password locks the CARootKeyRing.jks file. Specifying a value for this password is optional. You need to specify this password only if you want to be able to unlock the certificate authority files. Created when Specified when you install Agent Manager. Used when You need to specify the value for the certificate authority password only if you need to open the truststore files to examine the certificates that they contain.
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 Common agent registration OS All. Description This is the password required by the Common agent to register with the Agent Manager. User ID N/A. Created when Specified when you install Agent Manager. Used when Used during Common agent, Data agent, and Fabric agent installation. ITSOs user ID and password changeMe.
Group N/A.
85
Table 3-8 Common agent service logon user ID and password Item Common agent service logon user ID and password OS Windows. Description This creates a new service account under which the Common agent runs. User ID Created when Specified when you install Data agent or Fabric agent (only local). Password Used when N/A.
Group
Administrators.
N/A.
Table 3-9 Host authentication password Item Host authentication password OS All. Description N/A. Created when Specified when you install the Device server. Used when Used when you install Fabric agent to communicate with the Device server. ITSOs user ID and password tpctpc.
Group N/A.
User ID N/A.
Table 3-10 NAS filer login user ID and password Item NAS filer login user ID and password OS Windows. Description N/A. Created when Specified when you run NAS discovery. Password N/A. Used when N/A.
Group N/A.
User ID N/A.
86
Table 3-11 Resource manager registration user ID and password Item Resource manager registration user ID and password OS All. Description N/A. Created when Specified when you install Device server and Data server. Password password (by default). Used when Used when Device server and Data server have to register to Agent Manager. ITSOs user ID and password manager/ password.
Group N/A.
Table 3-12 WebSphere Application Server administrator user ID and password Item WebSphere Application Server administrator user ID and password OS All. Description You can use tpcadmin in order to avoid creating a new user ID and password. User ID If not provided, it will be created. Created when Specified when you install Device server. Used when Used when Device server has to communicate with WebSphere.
Group N/A.
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.
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
89
4. The DB2 Setup wizard window is displayed, as shown in Figure 3-10. Click Next to proceed.
90
5. You have to click I accept the terms in the license agreement if you accept the terms (Figure 3-11).
91
6. To select the installation type, accept the default of Typical and click Next to continue (Figure 3-12).
92
7. Accept the defaults and select Install DB2 Enterprise Server Edition on this computer (Figure 3-13). Click Next to continue.
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 Files\IBM\SQLLIB\. At this point, you can change the defaults as we did or accept the default configuration.
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
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.
95
11.In the Configure DB2 instances window, accept the default and click Next to continue (Figure 3-16).
96
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.
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.
98
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.
99
100
The DB2 installation proceeds and you see a progress window similar to the one shown in Figure 3-21.
101
16.Click Exit First Steps (Figure 3-23 on page 103) to complete the installation.
102
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-25 on page 105 shows the DB2 Windows Services that were created at the end of the installation.
104
105
Java error failure alternate command setupAix.bin -is:javahome ../ setupLinux.bin -is:javahome ../ setupLinux.bin -is:javahome ../ 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.
106
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.
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 Files\IBM\AgentManager\.
108
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.
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 Files\IBM\SQLLIB\. Database Name A default database called IBMCDB will be created for the Agent Manager. After entering the information, click Next to continue.
7. The Database User Information window is shown as Figure 3-31 on page 111. Enter the database user name and password. For these fields, use the DB2 administrator user ID that is in the DB2ADMNS group and the Administrator group (Figure 3-19 on page 99). If you want to use another user ID for the installation of Agent Manager, you can select Use a different user ID during the installation, and enter the user ID and password that you
110
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.
8. The WebSphere Application Server Connection Information window is shown in Figure 3-32 on page 113. Enter the following information, and click Next to continue: Host Name or Alias of Agent Manager Review the preinstallation task that is mentioned in 3.2.1 Verify the primary domain name systems on page 75. Use the fully qualified host name. For example, specify lead.itsosj.sanjose.ibm.com. This value is used for the URLs for all Agent Manager services. It is preferable to use the fully qualified host name rather than an IP address.
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 -an
112
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.
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.
114
10.In the WebSphere Application Server Connection Information window that is shown in Figure 3-34, accept the defaults and click Next to continue.
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.
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
13.In the Agent Manager Set Passwords window that is shown in Figure 3-37 on page 118, enter the following information and click Next to continue: Agent Manager Password This password is the resource manager registration password. This password is used to register the Data server or Device server with the Agent Manager. Enter the password twice. Note: The Agent Manager V1.2 installer provided a default user ID and password as manager and password. For Agent Manager V1.3.2, there is no default password. At the time of the writing of this book, entering a password other than password will cause the Data server and Device server installations to fail. Check the TotalStorage Productivity Center flashes to verify whether this situation has been fixed before entering a password other than password.
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.
118
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.
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.
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
The Agent Manager installation starts and you see several messages indicating the installation process. This normally takes about five minutes.
121
17.The next window you see shows the process checking the status of WebSphere running applications (Figure 3-41). Click Next to continue.
122
18.The Start the AgentManager Application Server window is shown in Figure 3-42. Choose Yes, start AgentManager now, and click Next to continue.
123
19.Next, you see the window shown in Figure 3-43, which indicates that the WebSphere server is starting the Agent Manager.
124
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.
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.
126
In Figure 3-47, verify that the ARS.version field shows the level that you have installed (in our case, it is 1.3.2.26). Confirm that you have received the message Health Check passed at the end of the HealthCheck utility listing, as shown in Figure 3-47.
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.
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.
128
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.
129
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).
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
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.
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).
132
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.
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).
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
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.
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.
136
10.The next window shows that the TotalStorage Productivity Center has been successfully installed (Figure 3-59). Click Finish to exit the InstallShield Wizard.
137
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>\log\dbSchema\install\dbSchemaInstallIS.log For Windows, the default InstallLocation is c:\Program Files\IBM\TPC. Check for the success message at the end of the log files to verify a successful installation.
138
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.
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.
140
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.
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).
8. In the window shown in Figure 3-64 on page 144, enter the following information: Data server name Enter the fully qualified host name of the Data server. Data server port Enter the Data server port. The default is 9549. Device server name Enter the fully qualified host name of the Device server. Device server port Enter the Device server port. The default is 9550. TPC Superuser Enter the Administrators Group for the TPC Superuser. We created the user ID tpcadmin and added this user ID to the existing Administrators
142
group. See 3.2.3 Using and defining user IDs and passwords on page 79 for more details. Host authentication password This is the password used for the Fabric agents to communicate with the Device server. Remember to record this password. See Table 3-4 on page 83. Data server account password For Windows only. TotalStorage Productivity Center installer will create an ID called TSRMsrv1 with the password that you specified here to run the Data server service. The display name for the Data server in Windows Services window is: IBM TotalStorage Productivity Center - Data Server WebSphere Application Server admin ID and password This is the user ID and password required by the Device server to communicate with the embedded WebSphere Application Server. You can use the TPC Superuser here. In our case, we used tpcadmin. Refer to Table 3-3 on page 82 for further details. If you click Security roles, the Advanced security roles mapping window is displayed. You can assign a Windows OS group to a role group for each TotalStorage Productivity Center role with which you want to make an association, so we can have multiple authority user IDs to perform various TotalStorage Productivity Center operations. The operating group must exist before you can associate a TotalStorage Productivity Center role with a group. You do not have to assign security roles at installation time; you can assign these roles after you have installed TotalStorage Productivity Center. If you click NAS discovery, the NAS discovery information window is displayed. You can enter the NAS filer login default user name and password and the SNMP communities to be used for NAS discovery. You do not have to assign the NAS discovery information at installation time; you can configure it after you have installed TotalStorage Productivity Center. Refer to 4.9.1 Manual NAS/NetWare server entry on page 345 for details. Click Next to continue.
143
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
Password This password is used to register the Data server or Device server with the Agent Manager. You previously specified this user ID during the Agent Manager installation (refer to Figure 3-37 on page 118). The default is password. Password - Common agent registration password This password is used by the Common agent to register with the Agent Manager. It was specified when you installed the Agent Manager (refer to Figure 3-36 on page 117). This password can be verified using the HealthCheck utility found under the <InstallDir>\IBM\AgentManager\toolkit\bin directory. Click Next to continue.
145
10.The Summary information window is displayed. Review the information, and then click Install to continue (Figure 3-66).
146
The installation starts. You might see several messages that are related to the Data server installation, which are similar to Figure 3-67.
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:\tpc33\disk1 C:\tpc33\disk2
148
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.
149
150
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).
152
2. The product selection window appears, as shown in Figure 3-72. Choose DB2 UDB Enterprise Server Edition and click Install New.
153
154
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.
155
156
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.
157
7. Select the installation directory where you want to install DB2. Click Next to continue (Figure 3-77).
8. The DB2 Administration Server (DAS) user window appears (Figure 3-78 on page 159).
158
Figure 3-78 DB2 Setup wizard: DB2 Administration Server user information
9. If you want the installer to create a DB2 Administration Server user ID, you must enter a unique user name for the DAS user in the user name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank and check Use default UID and Use Default GID, the system assigns a UID and a GID for you. Optionally, you can check Existing user and enter the name of an existing user ID, which will become the DAS user. After you have completed this panel, click Next.
159
160
10.Select Create a DB2 instance and click Next. The instance partitioning window appears (Figure 3-80).
161
11.Select Single-partition instance and click Next. The DB2 instance owner window appears (Figure 3-81).
162
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).
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).
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
15.If you do not have another DB2 server in your environment with an existing contact list, choose the default option of Local - Create a contact list on this system and click Next (Figure 3-84). If you do not enable the Simple Mail Transfer Protocol (SMTP) notification, you will receive a warning message. Click OK to the warning message to confirm that a setup without SMTP notification is intended.
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 window
166
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
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).
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
19.Each of the items displayed in the status report need to indicate Success. Click Finish to exit the DB2 Setup wizard.
169
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".
170
7. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command: su - db2inst1 8. Source the environment by issuing the following command: . ~/sqllib/db2profile 9. Type the following commands to shut down the DB2 environment: db2 force applications all db2 terminate db2stop db2licd -end exit 10.Switch to the DAS user authority. For example, if your DB2 DAS user is dasusr1, type the following command: su - dasusr1 11.Type the following commands to source the environment and shut down DB2 DAS: . ~/das/dasprofile db2admin stop exit 12.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/db2fix15 14.Install the Fix Pack by issuing the following command: ./installFixPak -b /opt/ibm/db2/V9.1/
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 owners 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 owners 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 exit
172
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.
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
4. The next window prompts you for the type and location of the database that is used for the Tivoli Agent Manager registry. You can choose among the following six options: DB2 database on this computer, which is the default DB2 database on another computer (without DB2 Administration Client) Local alias to DB2 database on another computer (using DB2 Administration Client) Oracle database on this computer Oracle database on another computer (using Oracle Database Client) Derby database on this computer We choose DB2 database on this computer, which is the default and suitable for our local installation of DB2.
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 Registry
176
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.
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, and
178
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.
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.
180
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.
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.
182
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.
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.
184
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.
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.
186
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.
187
16.The Agent Manager Application Server will be started immediately, as shown in Figure 3-103.
188
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.
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.
190
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 our installation, is named db2grp1: 1. Before you begin, log in to the Linux server as the root user; otherwise, you will not be able to perform this task. 2. Type the following at a command prompt: groups This command provides information about which groups contain the root user (Example 3-2).
Example 3-2 groups command output
[root@puget ~]# 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 users 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
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
Now, your system is ready for you to install the TotalStorage Productivity Center components.
192
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.
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.
194
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.
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.
196
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.
7. The window shown in Figure 3-112 on page 198 allows you to change the default space assigned to the database. Review the defaults and make any changes. In our installation, we accepted the default values. For better performance, we recommend that you: Allocate TEMP DB on another physical disk than the TotalStorage Productivity Center components. Create larger Key and Big Databases.
197
Select System managed (SMS), click OK, and click Next to proceed.
198
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.
199
9. The database schema installation begins. The TotalStorage Productivity Center installer provides you with progress updates, as shown in Figure 3-114.
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
3.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.
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.
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.
202
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.
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.
204
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.
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.
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
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
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.
208
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.
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.
210
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.
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.
212
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.
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.
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
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
216
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.
218
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).
219
4. Click Next. The Software License Agreement window appears (Figure 3-134).
220
5. You must click Accept and then click Next to proceed. The Select the Installation Type window appears (Figure 3-135).
221
6. Select Typical and then click Next. The Select the installation action window appears (Figure 3-136).
222
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).
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).
224
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).
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).
226
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
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).
228
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).
229
14.Click Do not prepare the DB2 tools catalog and then click Next. The Set up notifications window appears (Figure 3-144).
230
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).
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).
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
18.When DB2 has been successfully installed, an installation summary window appears (Figure 3-148).
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).
20.Each of the items in the status report needs to indicate Success. Click Finish to close the installer.
234
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".
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/bin
236
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.s061108 13.Install the Fix Pack by issuing the following command: ./installFixPak -b /opt/IBM/db2/V9.1/ 14.After the Fix Pack has been successfully installed, you must bind the database instance to the updated code by issuing the db2iupdt command. For example, if your instance name is db2inst1, and you installed DB2 in the default location, type the following commands: /opt/IBM/db2/V9.1/instance/db2iupdt db2inst1 15.Next, you must update the DB2 DAS. For example, if your DB2 DAS user ID is dasusr1, type the following command: /opt/IBM/db2/V9.1/instance/dasupdt dasusr1 16.Next, you must update the db2 instance owners 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 owners home directory. For example, if your instance is db2inst1, type the following command to change to that directory: cd /home/db2inst1/sqllib 17.Then, edit the userprofile contained in that directory. Add the following lines to the file and then save the file: EXTSHM=ON export EXTSHM db2set DB2ENVLIST=EXTSHM 18.Next, you must restart DB2. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command: su - db2inst1
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
238
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
240
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.
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.
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
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.
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.
244
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.
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
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.
248
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.
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.
250
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.
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.
252
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.
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.
254
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.
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.
256
257
258
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).
260
4. Click I accept the terms of the license agreement, and then click Next. The installation types window appears (Figure 3-167).
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).
262
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).
263
7. Enter the user ID for the DB2 instance owner in the Database administrator field, and enter the instance owners password in the Password field. Click Next to continue. The New Database schema information window appears (Figure 3-170).
8. You need to enter the DB2 instance owners user ID in the DB user ID field and the instance owners 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
9. The default entry in the Schema name field is TPC. We recommend that you do not change this field from the default setting. You then have the option of placing the various tablespaces in various directories or filesystems and of setting an initial database size. For all but the largest Enterprise deployments, database sizes of 200 MB are sufficient for the initial creation. For the best performance in medium and Enterprise deployments, consider placing the tablespaces on separate filesystems and on separate disk devices. If you have already created these filesystems, enter their paths in the Normal, Key, Big, and Temp fields, or click Browse to search for them. The Normal, Key, and Big databases can be housed in the same filesystem. The Temp database needs to be housed on a separate filesystem for the best performance. The differences between choosing System managed (SMS) and Database managed (DMS) containers are discussed in 2.3.3 SMS or DMS tablespace type on page 45. If you select Database managed (DMS), you can enter a path where you house log files and an initial size. Log files need to be housed separately from the tablespaces for best performance. For all but the largest Enterprise deployments, an initial size of 20 MB is sufficient.
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).
266
10.Click Install to begin the database schema installation. A progress window appears (Figure 3-173).
267
11.When the installation is complete, the installation results window appears (Figure 3-174).
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
3. Select the language from the drop-down list that you want to use for the installation, and then click OK. The TotalStorage Productivity Center Installer then initializes. The first item to display is the International Program License Agreement window (Figure 3-176).
269
4. Click I accept the terms of the license agreement, and then click Next. The installation types window appears (Figure 3-177).
270
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).
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).
7. Enter the user ID for the DB2 instance owner in the Database administrator field and the instance owners password in the Password field, and then click Next. The New database schema information window appears (Figure 3-180 on page 273).
272
8. Enter the DB2 instance owners user ID in the DB user ID field and the instance owners 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 servers 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.
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).
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
11.You can optionally enter group names to map to each specific role in TotalStorage Productivity Center, which provides you with more customized control over your management environment. When you have finished entering the information in the window, click OK. The Data server information window appears.
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).
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
When you have finished making your selections, click Next. The Agent Manager information window appears (Figure 3-184).
14.Enter the fully qualified host name of the Agent Manager server in the Hostname or IP address field. The Port (secured) and Port (Public) fields are populated with the defaults of 9511 and 9513, respectively. We recommend that you do not change them. In the User ID field, enter manager. In the Password field for that ID, enter password. These values are the defaults and cannot be changed. The default agent registration password is changeMe. Enter changeMe or enter the agent registration password that you created during the Agent Manager installation into the final Password field. When you have finished entering the information in this window, click Next.
277
278
15.Click Install. The Data server installation begins. A progress window appears (Figure 3-186).
279
16.When the installation completes, an installation results window appears (Figure 3-187).
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.
280
281
Java is a prerequisite for the Web GUI. You can verify its installation by running java -version, as shown in Figure 3-189.
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.
A security certificate approval window appears (Figure 3-191 on page 283). Depending on network transmission rates, it can take several minutes for the window to appear. At this point, you are prompted to start the TPC GUI. Click
282
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.
At this point, the Java applet for the TotalStorage Productivity Center GUI will download. The applet jarfile can take a while to load into your browser the first time. Be patient, because there is no progress bar displayed to indicate what progress is being made. After the applet jarfile has been loaded into your browser, it will remain in your browser cache until you dump it. Subsequent starts of the TotalStorage Productivity Center GUI load much faster. After the applet has loaded, it launches the TotalStorage Productivity Center GUI. In the center of the GUI, the Sign-on window appears. It is prefilled with the Server address and access port (9549 for TotalStorage Productivity Center V3.3). Enter your TotalStorage Productivity Center server User ID and Password, and click OK to continue (Figure 3-192).
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.
284
3. Edit the agent.config file in: For Windows: C:\Program Files\IBM\TPC\ca\subagents\TPC\Data\config\ For AIX and Linux: /opt/IBM/TPC/ca/subagents/TPC/Data/config Change serverHost= to your new Data Manager server name, as shown in Figure 3-194.
4. Restart the Tivoli Common agent service: Linux and UNIX environment: /opt/IBM/TPC/ca/endpoint.sh restart Windows environment, restart the following service: IBM Tivoli Common Agent-C:\Program Files\IBM\ca 5. During the restart of Common agent, the program finds the PROBE_ME file and checks the Data Manager server name from the config file and registers itself to the new Data Manager server.
285
286
Chapter 4.
287
288
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.
289
The steps are: 1. In the first window, select the preferred language for the installer (Figure 4-1).
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.
4. Click Next to continue. 5. In Figure 4-3 on page 291, you can choose the type of installation. We recommend that you always use Custom Installation when you install the agents. So, select Custom Installation by clicking the radio button next to it. In the window, you can also choose the installation path of the agents. The
290
default is C:\Program Files\IBM\TPC under Windows and /opt/IBM/TPC under UNIX and Linux. In our example, we keep the defaults. Note that the installer not only installs files in the location that you specify in this window, but there are also files, such as ep.reg, ep.bak, and the guid directory installed to the C:\Program Files\Tivoli\ directory under Windows. In the Linux and the UNIX environment, the installer installs the ep.reg file, ep.bak file, and the guid directory under the /usr/Tivoli/ and /opt/tivoli directories. Make sure that the installation location that you specify in this window is empty. Otherwise, the installer fails. Click Next to continue.
Figure 4-3 Local interactive installation: Type of installation and installation location
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.
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
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.
9. Click Data agent options. 10.In the window shown in Figure 4-6 on page 294, you can select two options: Agent should perform a scan when first installed Remove the check mark by this option if you do not want to have the Data agent perform an initial scan of your computer after installation. This option is checked by default. We suggest that you accept this default, so that you make sure that your Data server gets a solid information base about your computer immediately after installation.
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 servers \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 agents \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.
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.
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 Files\IBM\TPC\ca under Windows and /opt/IBM/TPC/ca under UNIX and Linux.
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
15.Enter the information and click OK, which will bring you back to the window shown in Figure 4-8 on page 296. Click Next.
297
16.The Summary Information window appears (Figure 4-10), where you can review the information that you have entered during the installation window.
17.Click Install to continue. The installer begins to install the Data agent (Figure 4-11 on page 299).
298
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.
299
Finally, a window appears announcing that the installation has finished successfully (Figure 4-12).
####################################################################### # (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. # # #
####################################################################### # # Custom Dialog: License # # The initial state of the License panel. The accept and reject option states # are stored as Variables and must be set with -V #
-V LICENSE_ACCEPT_BUTTON=true
####################################################################### # # Custom Dialog: License # # The initial state of the License panel. The accept and reject option states # are stored as Variables and must be set with -V #
-V LICENSE_REJECT_BUTTON=false
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 Files\My # Product, use # # -P installLocation="C:\Program Files\My Product" #
-P installLocation="C:\Program Files\IBM\TPC"
####################################################################### ####################################################################### # Dialog: dlgTPCProdInstallSel # # ####################################################################### # # Create Database Schema -V varCreateDBSchm="false" ####################################################################### # Data Server Installation -V varInstallDataSrv="false" ####################################################################### # # Device Server Installation -V varInstallDevSrv="false" ####################################################################### # # GUI Installation -V varInstallGUI="false"
302
####################################################################### # # 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
303
-V varCAPort="9510" ####################################################################### # # # Common Agent Registration Password -V varCAPassword="changeMe" ####################################################################### # # # CA Installation Location -V varCAInstallLoc="C:\\Program Files\\IBM\\TPC\\ca" ####################################################################### # # # Common Agent Service Name (For Windows only) # #-V varCASvcName= ####################################################################### # # # Common Agent Service User ID (For Windows only) # #-V varCASvcUsrID= ####################################################################### # # # Common Agent Service User Password (For Windows only) # #-V varCASvcUsrPW= ####################################################################### # # # Whether to install New Common Agent if it does not exist. -V varInstallNewCA="true" ####################################################################### 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.
306
or install both agents together. In the latter case, the TotalStorage Productivity Center Installer takes care of the proper sequence.
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/sshd
308
2. The International Program License Agreement is shown (Figure 4-14). Read and accept the terms by selecting I accept the terms of the license agreement.
309
3. In the window shown in Figure 4-15, choose Custom Installation. Click Next to continue.
310
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.
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.
312
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.
313
7. We want to enter our target computers manually, so we click Manually Enter Agents. The window in Figure 4-19 appears.
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.
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.
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
13.In this window, the TotalStorage Productivity Center Installer shows you the default installation directory for each target computer. Additionally in this window, you can also select two settings for the Data agents: Agent should perform a scan when first installed Remove the check mark from this option if you do not want to have the Data agent perform an initial scan of your computer after installation. This option is checked by default. We suggest that you accept this default so that you make sure that your Data server gets a solid information base about your computer immediately after installation. Agent may run scripts sent by server Remove the check mark from this option if you do not want the Data agent to be able to run scripts that the Data server sends. This option is checked by default. The advantage of selecting this option is that you can store scripts in the servers \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 agents \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.
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
The remote installation of the Data agent and the Common agent is now finished. The remote computers are now ready for the remote installation of the Fabric agents (if you choose to install them), because they now run a Common agent.
319
320
The install process creates a directory structure on the servers, which is similar to the directory structure shown in Figure 4-27 for a Windows server. For UNIX and Linux systems, the tree is created under /opt/IBM/ by default and otherwise looks the same.
Figure 4-27 Directory tree for Data and Fabric agent installation
321
Under Windows, you see one service, which is called IBM Tivoli Common agent (Figure 4-28).
The Data agent and Fabric agent do not show up as a service. They run under the context of the Common agent. Under UNIX and Linux, you see two processes. One process is the nonstop process, which launches the Common agent process, and the other process is the Common agent itself. The output of a ps -ef command shows the results in Figure 4-29.
Figure 4-29 UNIX and Linux process status after the agent installation
322
323
The following operational logs are for the Data agent when installed remotely for Windows: <InstallLocation>\logs\ <InstallLocation>\subagents\TPC\Data\log\<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>
324
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.
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.
326
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.
4. Click OK to continue. You see the TotalStorage Productivity Center Installer Welcome window (Figure 4-33).
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.
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
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.
330
The steps are: 1. To invoke the uninstall on a Windows computer, select Start Settings Control Panel Add/Remove Programs. You now see a separate entry for the Data agent. The uninstallation for the Fabric agent is invoked by selecting TotalStorage Productivity Center and clicking Change/Remove, as shown in Figure 4-37.
Figure 4-37 Local agent uninstall: Add or Remove Programs for remotely deployed agents
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
4. Now, the TotalStorage Productivity Center entry is gone and you have to select TotalStorage Productivity Center for Data - Agent, as shown in Figure 4-39. Click Change/Remove.
Figure 4-39 Local agent uninstall: Add or Remove Programs for remotely deployed agents
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
Figure 4-41 Local agent uninstall: Uninstall of remotely deployed Data agent
7. When the uninstallation has finished, you finally see a window announcing the successful uninstallation of the Data agent (Figure 4-42).
Figure 4-42 Local agent uninstall: Uninstall of remotely deployed Data agent completed
335
336
Figure 4-43 Copy the upgrade.zip file to the server upgrade directories
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
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
d. For alert log disposition, specify the number of days that you want Productivity Center for Data to keep alert records.
341
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.
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.
344
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.
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.
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
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.
347
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
The syntax to create the truststore for the TotalStorage Productivity Center server is: keytool -import -file <certificate-filename> -alias <server-name> -keystore vmware.jks
349
In our environment, which is shown in Figure 4-53, the command is: keytool -import -file rui.crt -alias faroe -keystore vmware.jks
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
6. Test the connection to the VMware VI data source by clicking Test VMware VI Data Source connectivity (Figure 4-55) to ensure that you can access information from the VMware data source.
7. After successfully connecting to the data source, run a discovery job for the VMware environment. The discovery is needed to retrieve every ESX Server instance that is part of the Virtual Infrastructure that has been added. The discovery mechanism is similar to a discovery for storage subsystems. Discovery jobs can be scheduled and are performed on the complete list of known VMware data sources.
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.
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
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.
353
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
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.
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.
356
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.
357
Figure 4-61 below shows the Alert tab with the single condition for this job that we can choose, which is Job Failed.
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
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).
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.
360
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.
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.
If we now examine the logs and we locate the failed part of the job, we learn that the errors are caused by failed logins, just as we expected. Note that the other parts of the jobs have completed successfully. These other parts are the logins and retrievals of information for the managed elements behind those CIMOMs, and these logins and retrievals do not require any authentication. 4. Next, we look at the CIMOMs that our discovery job has detected. We expand the Administrative Services Data Sources CIMOM Agents node of the Navigation Tree (Figure 4-66 on page 363). We now see an entry for each of the discovered CIMOMs. Those CIMOMs for which the login of the discovery job has been successful are marked by a green square and show SUCCESS for the connection status. Those CIMOMs for which no login can 362
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.
TotalStorage Productivity Center has now discovered three of our eight CIMOMs and was able to log in to one of those three CIMOMs.
363
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.
365
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
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 TotalStorage Productivity Center. However, the retrieval of the information about the managed elements (storage subsystems, tape library, and switch) has not yet occurred for those CIMOMs that require authentication. So, we have to run a further CIMOM discovery job. This CIMOM discovery job does not discover any new CIMOMs (as long as we did not add any new ones to our infrastructure in the interim). However, the CIMOM discovery job is now able to log in into each of the configured CIMOMs and retrieve all information about the managed storage subsystems, tape libraries, and switches.
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
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.
369
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
371
372
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. 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. Select the agent where Sybase or DB2 runs. Specify the instance or server name of Sybase and DB2.
373
User name and password of the Sybase or DB2 instance. The default port for Sybase is 5000 and for DB2 is 50000.
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.
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
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.
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-81 on page 377 and Figure 4-82 on page 378 show sample invoices generated with TotalStorage Productivity Center.
376
377
378
Chapter 5.
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).
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
The primary groups of the Navigation Tree relating to TotalStorage Productivity Center for Data are: Administrative Services: Mainly used for configuration of TotalStorage Productivity Center for Data itself IBM TotalStorage Productivity Center Data Manager Data Manager for Database Data Manager for Chargeback Each group is subdivided into functions: Administrative Services has the following sub-functions: Services: Used to view and control the various services that run in the Data Manager server. Data Sources: Used to control and view various agents/proxy components that are running on the monitored machines in your environment.
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
383
Services
When you expand Services and then click Data Server, you see the five services of the Data server (Figure 5-4).
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 required
384
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
385
The important values in this window (Figure 5-6) are: Service status, which is active Number of pending requests
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.
The additional functions, which are shown in Figure 5-7, include: View Log: All actions related to the service are written to the log. You can check the log to define the problem, to report the problem to the support center, and to check the status of the service, such as when it is started, initialized, or shut down. Errors are shown in the color red. If you are unable to see the logs, you can alternatively check the logs from the operating system: For the server component: C:\Program Files\IBM\TPC\Data\log\server_xxxxxx.log For the Scheduler component: C:\Program Files\IBM\TPC\Data\log\Scheduler_xxxxxx.log For CIMOM component: C:\Program Files\IBM\TPC\Data\log\cimom_xxxxxx.log For the agent component: C:\Program Files\IBM\TPC\Data\log\TPCD_xxxxxx.log Figure 5-8 on page 387 shows a sample Scheduler log display in the content pane.
386
Configure tracing by right-clicking the desired service and selecting Configure Tracing (Figure 5-7 on page 386). When reporting a problem, you might be asked to produce a trace related to that service. In that case, enable the trace and provide the report to the support center for debugging. In this window (Figure 5-9 on page 388), you can enable the trace and define the trace level as DEBUG_MIN, DEBUG_MID, or DEBUG_MAX. Figure 5-9 on page 388 shows the Configure Tracing pop-up window for the GUI and the Server. Note that the Server Tracing configuration also allows you to specify the number and the size of the trace logs. The following example of the path and naming convention for the Trace log files is for the Server component: C:\Program Files\IBM\TPC\Data\log\ServerTrace.log
387
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
When you double click the particular Data Agent, you see high level information about that Data agent in the content pane. The information window has three tabs, General, Detailed and Jobs, which we describe in the following sections.
389
General tab
The following information is available under the General tab (Figure 5-11): Agent status Port Host Address Last update Time zone Connection Errors Consecutive Errors The important values are the agent status and the errors.
390
Details tab
The following information is available under the Details tab (Figure 5-12): Agent name Host name Host ID (This inclusion is new to TotalStorage Productivity Center V3.3.) Start Time Elapsed Time VM Size Manufacturer OS Type CPU Architecture Job Count
391
Jobs tab
If there is any job that is currently running for this agent, you can see the following information, as shown in Figure 5-13: Schedule name Job name Run Job Status Scheduled time Started time
392
Data Manager enables us to generate and use reports easily by using the predefined reports in the Navigation Tree entry titled My Reports. This section is divided into the subnodes discussed in the following sections. Note: We do not show all of the possible reports in detail in this section. For certain reports, we only provide a description of how to generate the report or a short description of the purpose of the report.
System Reports
System Reports (Figure 5-14) are predefined in the TotalStorage Productivity Center and are prepared automatically for the monitored machines. In this section, we provide the steps to create the reports and summary information about the reports. We show examples of selected predefined reports. When the reports are displayed in the content pane, you see either a pie chart icon, a magnifying glass icon, or both icons. Clicking the pie chart icon displays the report in a graphical pie chart form. Clicking the magnifying glass icon gives you the report details in a tabular form.
393
Complete the following steps to generate an Access Time Summary report for all of your servers: 1. Select IBM Total Storage Productivity Center My Reports System Reports Data Access Time Summary (Figure 5-16 on page 395).
394
2. Click the Selection tab in the top left of the Report Filter Specifications. 3. Select the profile and columns to include or exclude and click Generate Report. 4. The first report is Network-wide, as shown in Figure 5-17.
395
5. Click the pie chart icon to view the report in the pie chart format, as shown in Figure 5-18.
To generate a report for an individual server, complete the following steps: 1. Select IBM Total Storage Productivity Center My Reports System Reports Data Access Time Summary. 2. Click the Selection tab in the top left of the Report Filter Specifications. 3. Select the profile and columns to include or exclude and click Generate Report. 4. The first report is Network-wide. Click the magnifying glass icon to list the available servers, as shown in Figure 5-19 on page 397.
396
5. Click the magnifying glass icon or the pie chart icon to the left of a particular server to see the report for the selected server, as shown in Figure 5-20.
397
The amount of free space on disk Raw volume space The amount of space used by Redundant Array of Independent Disks (RAID) or mirroring You can generate a report by using the following steps: 1. Select IBM Total Storage Productivity Center My Reports System Reports Data Disk Capacity Summary. 2. Click the Selection tab in the top left of the Report Filter Specifications, as shown in Figure 5-21.
3. Select columns to include or exclude and click Generate Report. 4. The first report is Network-wide, as shown in Figure 5-22.
5. Click the magnifying glass icon to see the report for all servers (see Figure 5-23 on page 399).
398
399
You can generate a report by completing the following steps: 1. Select IBM Total Storage Productivity Center My Reports System Reports Data Disk Defects, as shown in Figure 5-24.
2. Click the Selection tab in the top left of the Report Filter Specifications. 3. Select columns to include and exclude and click Generate Report. The first report is network-wide. 4. Click the magnifying glass icon or the line chart icon next to each line to see the report for the selected server, as shown in Figure 5-25 on page 401.
400
401
2. Click the Selection tab in the top left of the Report Filter Specifications, as shown in Figure 5-26.
3. You can also select the computers from the list or perform filtering depending on the columns that are available. 4. The report shown in Figure 5-27 on page 403 shows you the oldest files, which have been modified but not backed up. The report is sorted by computer name.
402
5. You can also select the computers from the list or filter the information depending on the columns available.
403
Tivoli Storage Manager backup and archive from Most at Risk Files
To initiate backup and archive to the Tivoli Storage Manager Server, perform the following steps: 1. Highlight the line or lines for each file. You can use the Shift key to select a group of files or the Ctrl key to select an individual file, as shown in Figure 5-28.
Figure 5-28 Select files to back up from Most at Risk Files report
2. Right-click and the Selection pop-up window appears (Figure 5-29 on page 405): a. Select Create a new archive/backup job to run a new job. b. Select Add to an existing archive/backup to add the list to an already created job.
404
3. Select the type of backup that you want to run (see Figure 5-30): Archive Selective backup (Full backup) Incremental backup
405
4. Define any extra option for the Tivoli Storage Manager server by selecting the appropriate tabs. Figure 5-31 shows the options under the When to Run tab, and Figure 5-32 on page 407 shows the Alert tab options.
406
Figure 5-32 Tivoli Storage Manager Create File Archive/Backup Action: Alert options
5. Press Ctrl+s to save or click Save to create the job. 6. You can follow the job status by selecting Data Manager Policy Management Archive/Backup Job name.
407
408
409
410
3. Select the report type, as shown in Figure 5-37. You can select the following reports: Asset System-wide Storage Subsystems Availability Capacity Usage Usage Violations Backup Groups
411
4. Click the Options tab to define the batch output, as shown in Figure 5-38. The options include: Select Agent computer to run the batch report job. Select output format: Comma separated value (CSV) Formatted File HTML File
Select the format for the output file name (see Example 5-1).
Example 5-1 Batch report format
{Report creator}.{Report name}.{report run number} TR50411.batch-report1.001.HTML 5. Click the When to Run tab to define the schedule time. 6. Press Ctrl+s to save the batch report. The job will be submitted at the specified time and day. You can follow the status by selecting Data Manager My Reports Batch Reports.
412
7. The batch report output is saved to the specific directory of the agent machine with the name that you specified in the Options tab: For Windows, the output is saved in: \Program Files\IBM\TPC\ca\subagents\TPC\Data\log\<computername>\reports\ For UNIX, the output is saved in: /opt/IBM/TPC/ca/subagents/TPC/Data/log/<computername>/reports/
5.2.3 Probe
Probe jobs collect detailed statistics about all of the assets of the managed infrastructure, such as computers, disk controllers, hard disks, clusters, fabrics, storage subsystems, logical unit numbers (LUNs), virtual machines, tape libraries, and filesystems. Probe jobs can also discover information about new or removed disks and filesystems. Probe jobs can be directed against any elements in the managed infrastructure. In our examples, we run probe jobs against storage subsystems, fabrics, and computers. To create the probe job, complete the following steps: 1. Select IBM Total Storage Productivity Center Monitoring Probes. 2. Right-click and select Create Probe. 3. You can select what to probe, such as a computer, computer groups, clusters, storage subsystem groups, or storage subsystems. 4. You can create separate probe jobs for various groups. 5. Select job schedule characteristics, such as run immediately, run once at a certain time, or run several times. 6. Save to create the probe job. 7. You can follow the status of the probe job by selecting IBM Total Storage Productivity Center Monitoring Probes probe-job-name date-time-of-run.
413
Figure 5-39 shows all of the elements of the probe job in one window.
414
If you have installed IBM TotalStorage Productivity Center for Replication on a different system, follow the below steps to configure TotalStorage Productivity Center main GUI: 1. Right-click IBM TotalStorage Productivity Center External Tool, as shown in Figure 5-40.
2. Enter the Hostname/IP address of the TPC-R server, as shown in the Figure 5-41and click save.
415
3. Click the Launch button to launch the IBM TotalStorage Productivity Center for Replication from the IBM TotalStorage Productivity Center GUI, as shown in Figure 5-42
4. The external tool is added under IBM TotalStorage Productivity Center External Tools Label, where <Label> is the definition in the Label field.
416
5.3.1 Monitoring
The monitoring function enables us to run regularly scheduled or one-time data collection jobs. These jobs gather statistics about storage assets and usage within the environment. You can use the information gathered by monitoring jobs to set alerts, enforce policies, and generate detailed reports. Determining what information you want to gather about your storage resources is critical to helping you implement a storage management strategy. Once you have determined the types of information you want to collect about your storage resources, you can use monitoring jobs to collect that information according to a schedule that you define. Storage resources that Data Manager can collect information about includes computers, clusters, disk controllers, hard disks, NAS Filers, and filesystems. The data and statistics gathered by monitoring jobs are stored in the database repository and are used to supply the data necessary for reports. The following sections give a detailed description of the sub-menus under Monitoring.
417
Groups
A group represents a set of user-defined objects against which you can run monitoring and reporting jobs. It enables you to define a set of related objects one time and save these selections as a named group for future use in scans, pings, and other entities within the Data Manager. This section describes the possible groupings. Computer: A computer group is a logical grouping for related computers. A computer can belong to one computer group only. A computer will automatically be removed from a group if you add it to another group. Use computer groups to monitor computers that are related to each other or belong to a common group such as a department, a location, a territory, and so on. To create a computer group, perform the following steps: a. Select Data Manager Monitoring Groups Computer. b. Right-click and select Create Computer Group. All available computers are listed. c. Double-click a computer to add a computer to the group under Current Selections. d. Press Ctrl+s to save the group with a new name. A pop-up window asks for the name of the group (Figure 5-44). Enter the computer group name and press OK.
Filesystem: The filesystem group is a grouping of filesystems in computers. A filesystem can belong to one filesystem group only. A filesystem will automatically be removed from a group if you add it to another group. To create the filesystem group, perform the following steps: a. Select Data Manager Monitoring Groups Filesystem.
418
b. Right-click and select Create Filesystem Group. The list of available computers and their filesystems appears. c. Expand the computer name to display the filesystem names (Figure 5-45). d. Double-click the filesystem name to include in the group. e. Press Ctrl+s to create and save the group.
Directory: A directory group is the grouping of directories in computers. You can include a directory in multiple directory groups. To create the directory group, complete the following steps: a. Select Data Manager Monitoring Groups Directory. b. Right-click and select Create Directory Group. c. Click New Computer. d. The Edit directories for computer pop-up window appears. e. Select the computer or all computers. f. Edit the directory name and click Add. Important: TotalStorage Productivity Center for Data does not check the syntax or whether the directory is available. Be careful that you add directories that are actually available; otherwise, the group reports for the groups do not contain any data. g. For another directorys information, repeat Steps 3 to 6.
419
h. Each time that you add a directory for a computer, the computers information does not display on the next Edit directories for computer window. To add a new directory to the computer, you must perform the following steps: i. Right-click the computer name and select Edit. The Edit directories for computers pop-up window appears for the selected computer. ii. Add a new directory and press OK. i. When all of the directories are added, press Ctrl+s to save the grouping information (Figure 5-46).
User: This function groups users on all computers. A user can belong to one user group only. To create a user group, perform the following steps: a. Select Data Manager Monitoring Groups User. b. Right-click and select Create User Group. All available users are listed. c. Double-click a user to add a user to the group under Current Selections.
420
d. Press Ctrl+s to save the group with a new name. A pop-up window asks for the name of the group (Figure 5-47). Enter the user group name and press OK.
OS user group: The OS user group is a grouping of users that is defined in the operating system as a user group. We can create OS User Groups in the same way as we created the User Group above.
Ping jobs
The Ping job collects information about the availability of the storage assets in your environment. By running pings and viewing the results of those pings in Reporting Availability reports, you can monitor and report on the availability of your storage, both from a network point of view and from a computer uptime perspective. To create the Ping job, complete the following steps: 1. Select Data Manager Monitoring Pings.
421
2. Right-click and select Create Ping. You can add a computer, computer groups, or clusters for the Ping job to run against (Figure 5-48).
3. You can create separate Ping jobs for multiple groups, for example, one Ping job for computers that have DB2 and one Ping job for Linux computers. 4. Select job schedule characteristics, such as run immediately, run once at a certain time, or run several times at regular intervals. 5. You can also set up alerts for triggering an action like SNMP traps, running a script, sending an e-mail, and so on, when a certain condition is met. The default setting is Computer Is Unreachable More Than certain number of times. No other alerting conditions are currently available. 6. Press Ctrl+s to create and save the Ping job. 7. You can follow the status of the Ping job by selecting Data Manager Monitoring Pings ping-job-name date-time-of-run. See Figure 5-49 on page 423.
422
Scans
The Scan job collects statistics on the usage of storage. Detailed usage information is stored in the Data Manager repository and we can see those details in the form of reports. To create the Scan job, perform the following steps: 1. Select Data Manager Monitoring Scans.
423
2. Right-click and select Create Scan. You can add filesystems, a computer, computer groups, or clusters to the Scan job, which runs as shown in Figure 5-50.
3. You can add specific directories to the Scan job: a. Click the Directory Groups tab. b. Select the Available Directory Groups or create one by clicking New Directory Group. c. Click New Computer. d. A pop-up window appears. Select the computer name from the list, add the directory for the selected computer, and click Add. e. Click OK and save the directory group by pressing Ctrl+s. 4. Select the Profile tab to customize the Scan job, as shown in Figure 5-51 on page 425. Select the profiles according to the requirements.
424
5. Click the When to Run tab to select job schedule characteristics, such as run immediately, run once at a certain time, or run several times. 6. You can also set up alerts for triggering an action like SNMP traps, running a script, sending an e-mail, and so on, when a certain condition is met. The default condition is Scan Failed. No other condition is available so far. 7. Save to create the scan job. 8. You can follow the status of the scan job by selecting Data Manager Monitoring Scans scan-job-name date-time-of-run.
425
Profiles
Profiles enable you to define which statistical information you plan to gather
during the Scan. TotalStorage Productivity Center for Data comes with a predefined set of profiles. You can find the information about default profiles in Table 5-1.
Table 5-1 List of profiles Description Statistic about the number of files that are modified (longest) but not backed up since they were modified (the default is 20 files) (Windows only). Statistics about the file based on its access time. Statistics about the file based on its creation time (Windows only). Statistic about files that are modified but not backed up since the modification (Windows only). Statistics about files by the length of time since the last modification. Information about the size of the files. Statistics for a certain number of the largest directories (the default is 20 directories). Statistics for a certain number of the largest files (20 files are the default). Statistics for a certain number of the largest orphan files. Orphans are the files that have no owner since the time that they were created (the default is 20 files). Statistics for a certain number of the most obsolete files. Obsolete files are files that have not been modified or accessed for a long time (the default is 20 files). Statistics for a certain number of the oldest orphans (the default is 20 files). Summary based on file type.
426
Profile name Summary By Filesystem/Directory Summary By Group Summary By Owner Temporary Files
Description Summary based on filesystem/directory. Summary based on groups. Summary based on owner. Statistics for files that are not owned by the operating system and have not been accessed in one year. Statistics for space usage for space that is not owned by the operating system and that has not been accessed in one year.
Wasted Space
You can also define your own profiles. To create a user-defined profile, perform the following steps: 1. Select Data Manager Monitoring Profiles. 2. Right-click and select Create Profile. 3. In the Statistics tab, you can define several options for the files that will be included in the Profile (Figure 5-52 on page 428): a. Summary space usage by: Filesystem Owner Group File types Last access Creation Last modification Last modification (not backed up) Size of the distribution Largest file Largest directories Most obsolete files Most at risk files Largest orphaned files Oldest orphaned files
427
5. Press Ctrl+s to save and create the Profile. Continue to use these windows if you want to create more profiles with your own definitions.
5.3.2 Alerting
Alerting is used to inform the TotalStorage Productivity Center administrator when certain conditions occur on the devices that are monitored. TotalStorage Productivity Center for Data collects statistics for the computer, storage subsystems, filesystems, directories and VMware ESX Server. You can set certain thresholds to detect the problem or events that might create problems later, so that storage administrators can be proactive to correct potential problems. Once you have defined the events or conditions for which you want to be alerted, you can let Data Manager monitor your storage so that you do not have to.
We can define four types of alerts under Data Manager. The four types of alerts are Computer Alerts, Filesystem Alerts, Directory Alerts, and Hypervisor Alerts.
428
3. The next window, which is shown in Figure 5-54, is the Create Alert window where you define your alert.
429
4. When you select the Alert tab, you can use the Triggering Condition drop-down list to select one of the alert types shown in Figure 5-55.
5. In the Triggered Actions area, select the actions that will occur as a result of the triggering condition.You can trigger SNMP Trap, TEC Event, Login Notification, Windows Event Log, Run Script, or Email. 6. After you have selected the type of alert and the action on alert, select the Computers tab to associate the alert to one or more of your resources, as shown in Figure 5-56 on page 431.
430
7. Press Ctrl+s to save the alert. These alert conditions might be detected by a probe job. The following predefined alert conditions are available. Note that this list is subject to change and might be incomplete or might contain extra entries: RAM increased RAM decreased Virtual memory increased Virtual memory decreased New disk detected Disk not found New disk defect found Grown disk defect found Disk failure predicted New filesystem detected Virtual server added Virtual server removed Virtual server moved Computer Unreachable Computer Discovered
431
Computer Status Change Offline Computer Status Change Online Computer Property Change Host bus adapter (HBA) Driver Version Change HBA Firmware Version Change Cluster Resource Group Added Cluster Resource Group Removed Cluster Resource Group Moved The above Cluster Related Alert Conditions are only for HACMP on AIX. The steps to create the alert for HACMP is same as a regular one. You can select only one condition at a time. If you want to detect several conditions, you must define a separate alert for each condition.
Filesystem alerts
You can use these alerts to monitor filesystems for available free space, changes in configuration, or if a filesystem being removed or unmounted. These alerts are detected by the Scan job.When the condition is detected during a scan, an alert is generated. Filesystem alerts can be applied to filesystems, filesystem groups, computers, computer groups, and clusters. The following predefined alerts are available: Filesystem not found Filesystem reconfigured Filesystem freespace less than X (percentage, KB, MB, or GB) You have to enter a threshold value for this condition. Free UNIX Filesystem (FS) Inode less than X (percentage or inodes) You have to enter a threshold value for this condition. As an example, let us define an alert for Filesystem Freespace less than 30 percent. Complete the following steps to create the alert: 1. Select Data Manager Alerting Filesystem Alerts. 2. Right-click and select Create Alert. 3. Select Filesystem Freespace less than from the condition list (Figure 5-57 on page 433). 4. Enter 30 for the Value and select percent from the Value Units drop-down list. 5. Select a triggered action to occur when the condition is met. We select Windows Event Log and the Warning type. 6. Click the Filesystems tab and select which machines to notify.
432
Directory alerts
You can use these alerts to be notified when either a directory is not found or a directory consumes more than a specified amount of storage space. These alerts are detected by the scan job. When a condition is detected during a scan, an alert is generated. These alerts can be applied to directories and directory groups. The following predefined alerts are available: Directory not found. Directory consumes more than X (percentage, KB, MB, or GB). You have to enter a threshold value for this condition. As an example let us define an alert for a directory consuming more than 2 GB. Complete the following steps to create the alert: 1. Select Data Manager Alerting Directory Alerts. 2. Right-click and select Create Alert. 3. Select Directory Consumes More Than from the condition list.
433
4. Enter 2 for the value and select Gigabytes from the list (Figure 5-58). 5. Select a triggered action to occur when the condition is met. We have selected Windows Event Log and the Warning type. 6. Select the directories for which you want to set alerts. 7. Press Ctrl+s to save the alert.
Hypervisor alerts
The latest version of TPC has a new alert feature for VMware ESX Server. The following alert conditions are supported for VMware ESX Server: Hypervisor Discovered Hypervisor Missing Virtual Machine Added
434
Virtual Machine Removed To configure the alert for VMware ESX Server, follow these steps: 1. select Data Manager Alerting Hypervisor Alerts. 2. Right-click and select Create Alert, as shown in Figure 5-59.
3. Select the applicable triggering condition. 4. Select a triggered action to occur when the condition is met. 5. Go to the Hypervisor tab to select the ESX Server for which you want to set the Alert.
435
Alert Logs
Whenever an alert condition occurs for any of the alerts, it makes an entry to the Alert Log apart from triggering the specified action. After running the probe or scan job, you can check the Alert Log to see which conditions for which alerts have been met. As an example, we have created a Computer Alert with the Computer Unreachable condition and have run the Probe job. Some of the computers, which met the alert condition, have been detected. The following steps take you to the Alert Log: 1. Select IBM TotalStorage Productivity Center Alerting Alert Log. 2. Select All or Computer from the subtree.
436
3. The report displays if there is at least one machine that satisfies the alert condition: a. Check the alert type to see the condition. b. Check the alert name and alert creator to see which alerts have been satisfied. 4. In our example (Figure 5-61), the alert log shows all the computers that have met the Unreachable Condition.
5. To get more information, click the magnifying glass icon (detailed information is shown in Figure 5-62).
437
As you can see, there are six areas under policy management: Quotas Network Appliance Quotas Constraints Filesystem Extension Scheduled Actions Archive/Backup In general, you can observe: If there is a plus sign in front, there are either more items that you can browse, or there are already user-defined entries. If there is no plus sign in front, there is no user-defined entry yet. With policy management, we have no predefined definitions of any type.
438
Quotas
You can set limits on the amount of storage that a user or a group of users can consume. A user can work on one computer or several computers. With TotalStorage Productivity Center for Data, you can define quotas for multiple levels: Network Level: Define a quota that place limits over multiple machines. Computer Level: Define a quota that places limits on a specific machine for a user or group of users. Filesystem Level: Define quotas for a user or group of users at the filesystem level. They are available for a single User or OS User Groups. With this capability, a user can only consume that storage that is allowed. At the same time, you can allow a user to consume more storage on one computer while limiting that user to consuming less storage on another computer. And in total, you can limit a user to consume a specified total amount of storage within the whole environment. Note: Quotas allow users to exceed the limits. Quotas just alert the system administrator or storage administrator about the quota violations. You can limit a user to use a certain amount of storage by using operating system utilities. To create a quota, perform the following steps: 1. Select Data Manager Policy Management Quotas User or OS User Group. 2. Select Network, Computer, or Filesystem from the subtree depending on which level of quota you want to control. 3. As an example, select Computer and right-click and select Create Quota. 4. The window displays the list of users. Select a user or users from the list and add that user or users to the selection window. 5. Click the Computers tab to see the list of computers or computer groups. 6. Select the computer, computers, or computer group to limit the user for the selected computers. 7. Click the Alert tab to define the quota for the user. 8. As an example, enter the value of 200 MB. 9. Schedule the job by selecting the When to Run tab.
439
Note: To have an up-to-date filesystem as opposed to quota information, plan to run the quota job after the scan job. The Data Manager then compares the filesystem information against the defined quotas, because the scan job collects and updates the latest status of the filesystem to Data Manager Repository. 10.Press Ctrl+s to save the Quota job. 11.To see the result of the job, select Data Manager Policy Management Quotas User Computer quota-name date-time of job (Figure 5-64).
12.To see the list of users who have violated the quotas, click IBM Total Storage Productivity Center Alerting Alert Log All, as shown in Figure 5-65 on page 441.
440
441
Constraints
Constraints are used to limit the user from putting restricted or unacceptable file
types (such as MP3 files) on the monitored machine. You can define a constraint violation so precisely that you are able to detect violations committed by a certain user and regarding a certain file or file type. The following three default constraints are available: TPCUser.AtRiskFile Constraint TPCUser.ObsoleteFile Constraint TPCUser.Orphaned File Constraint To create the new constraint, do the following steps: 1. Select Data Manager Policy Management Constraints. 2. Right-click and select Create Constraint. 3. Select Filesystem or computers from the list in the Filesystem tab.
442
4. Click the File Types tab: a. You can either forbid or allow certain file types. b. You can choose predefined file types or add your own pattern, as shown in Figure 5-66.
443
5. Click the Users tab (Figure 5-67). You can either forbid or allow certain file types owned by selected users.
6. Click the Options tab (Figure 5-68). You can define an: a. Alert on files that have not been accessed in more than a specified number of days. b. Alert on files that are bigger than a specified number (byte, KB, MB, GB, or TB). c. Alert on files that have set-UID root. d. Alert on files that have not been backed up (Windows only) since they were modified in more than a specified number of days.
444
7. All of the constraints that you have selected in the previous three steps can be seen in File Filter Text in the Options window. You can directly add new conditions or change the previously set conditions from this window. Here are examples: a. (NAME matches any of ('*.avi', '*.jpg', 'itso*.*') AND TYPE <> DIRECTORY) Restrict files that match a certain file pattern. b. SIZE > 100 MB Alerts on files whose size is greater than 100 MB. c. ((NAME matches any of ('*.jpg', '*.mp3') AND TYPE <> DIRECTORY) OR OWNER matches any of ('guest')) Restrict certain file types and guest user.
445
8. To add a new condition, perform the following steps: a. In the Options window, click Edit Filter. b. The Edit Filter pop-up window appears (Figure 5-69). c. Highlight the line and right-click. The following options appear: New Condition New Group Merge Edit Delete Cut Copy Paste
d. Click New Condition. A Create Condition pop-up window appears (see Figure 5-70 on page 447).
446
e. A pop-up window is context sensitive. Depending on the selected condition, the window changes accordingly. f. As an example, select Name, edit the Match value, and click Add. g. As an example, select Attributes, select one of the attributes from the pull-down list (for example, Executable), and click Add. 9. Click the Alert tab to set the triggering-condition. 10.Press Ctrl+s to save the constraint.
Scheduled actions
TotalStorage Productivity Center for Data can be used to schedule any script against the monitored servers. Tip: The Triggered action facility is used to run the scripts when certain alerts are set. However, scheduled actions can be run whenever you want without waiting for an alert condition.
447
Scripts work in the following way: 1. During installation, TotalStorage Productivity Center for Data creates the following directory on every server and agent machine: \Program Files\IBM\TPC\ca\Subagents\TPC\Data\Scripts for the Windows agent /opt/IBM/TPC/ca/subagents/TPC/Data/scripts for the UNIX agent \Program Files\IBM\TPC\Data\Scripts for the Windows server /opt/IBM/TPC/data/Scripts for the UNIX server 2. When the scripts run, TotalStorage Productivity Center for Data server looks in its local \scripts directory. 3. If the server finds the script, it loads it and sends it to the agent machine where you designated the script to be run. 4. The agent checks its local script directory. 5. If the agent finds a local version of the script, it ignores the script sent by the server and runs the local version. 6. If there is no script with the same name in the local agent script directory, the agent receives the script from the server, saves the script with a temporary name, and runs the script. After the script runs, the agent deletes the script. Important: If the script that you prepared on the server does not run, then check to: Make sure that no script with the same name is on the agent script directory. Make sure that the agent is installed by enabling the Agent may run script sent by server option. To run the script, perform the following steps: 1. Select Data Manager Policy Management Scheduled Actions Scripts. 2. Right-click and select Create Scripts. 3. Click the Computers tab. Select the computers on which you want to run the script. 4. Click the Scripts Options tab. Select the script from the drop-down list. These lists are derived from the server script directory. If you want to create a new script, then edit one and put it into the server script directory. 5. Click the When to Run tab and define the scheduled time for the script.
448
6. Press Ctrl+s to save the script. 7. You can check the script status by selecting Data Manager Policy Management Scheduled Actions Scripts script-name date and time.
Archive/Backup
You can integrate TPC with IBM Tivoli Storage Manager to archive or backup files. Use the Archive/Backup facility to view and edit IBM Tivoli Storage Manager archive and backup jobs that were defined to run against the files selected from the following reports: Reporting Usage Files Largest Files Reporting Usage Files Most Obsolete Files Reporting Usage Files Orphan Files Reporting Usage Files Duplicate Files Reporting Backup Most At Risk Files Reporting Usage Violations Constraint Violations Refer to Figure 5-71, which shows the pop-up window that comes when you try to create Backup/Archive Job from this window.
The way that an Archive or Backup job is defined differs from the other job definitions. These Archive and Backup jobs are defined on the files that you identified as a result of a certain report. Therefore, you must first define a report, which is able to determine a list of files, and then you create the Tivoli Storage Manager Backup or Archive job on that list of files. These jobs are displayed and managed from here.
449
For additional information about creating a Tivoli Storage Manager backup job, refer to Tivoli Storage Manager backup and archive from Most at Risk Files on page 404.
5.4 Reporting
Use the Reporting facility of Data Manager to view both overview and detailed information about your storage. The more than 300 available reports are constructed from the statistical information collected by monitoring jobs and accumulated in the repository. The reporting features are very powerful, allowing you to select exactly the computers, storage subsystems, disks, filesystems, and even users upon which you want to report. You can view reports as tables of data or as graphical charts, which provides you with the flexibility to get a very detailed look at your information or a very high level overview. The following major sections are available for reporting under Data Manager: Groups Asset Availability Capacity Usage Usage Violations Backup To better demonstrate all of the reporting types, refer to Figure 5-72 on page 451. Note that not all entries are fully expanded.
450
Generally, remember that when using the reporting feature in Total Storage Productivity Center that all reports are to be seen as a base for your own reports. When you make any modifications, such as defining another scope, that is, you define the report to run on a single computer, the reports is going to be run in one of the following two ways: You run this report just one time. You save the report definition and the report shows up under the My Reports option in the Navigation Tree view.
451
5.4.1 Groups
Groups are a means to define subsequently defined reports against specific groups of computers or filesystem groups. Groups are advantageous, because they provide you with the capability of logically grouping many computers in one predefined group. As described earlier, the way to define this type of group follows the same principles, and we do not go into any more detail here.
5.4.2 Asset
Asset reporting enables you to view information about the agents, clusters, computers, disks, storage subsystems, controllers, and filesystems, and general hardware inventory of storage assets within your environment. While running probes, it itemizes the information about your storage assets and provides a hierarchical view of that information so you can drill down to view your assets in greater detail. The following subcategories enable you to change your view of asset reports: Cluster Computer OS type Storage Subsystem System-wide A detailed overview of these subcategories is given below. Note: Within the Asset subtree, all of the available selections display the related information on the right side of the GUI, either in a tabbed view or in a plain view. There are no definitions, subselection, or further refining available. The basic approach is just to click to see what information displays.
By Cluster
This reporting category shows the assets based on Microsoft Cluster Services (MSCS) cluster membership. Clusters are subdivided into nodes and virtual servers. For each virtual server, you can see controllers, disks, filesystems, logical volumes, and exports or shares. TotalStorage Productivity Center V3.3.2 allows you to see the asset report for HACMP on AIX. Figure 5-73 on page 453 shows an example for asset reporting for HACMP on AIX
452
To get the asset information for HACMP on AIX, select Data Manager Reporting Asset By Cluster. You get a detailed description about the cluster being monitored by TPC and the respective Cluster Resource Group and the Virtual Nodes.
By Computer
In this reporting category, each computer in the environment is listed. Depending on the computer operating system type, each computer is subdivided into: Controllers Disks Volume groups Filesystems Exports or shares Monitored directories We will show you examples with AIX, Linux, or Windows computers asset reports.
453
To get assets for one of the machines, perform the following steps: 1. Select Data Manager Reporting Asset By Computer. 2. All of the computers are listed. Select one of the computers. In our example, we selected Lead.itsosj.sanjose.ibm.com (see Figure 5-74).
The report displays detailed information about the machines architecture and storage in the content pane as soon as you select the computer. Information displayed includes Hardware Details, Operating System Details, Disk Capacity Details, and so on.
454
To get detailed information for each component of a machine, you can select the following subtrees: a. Controllers: This selection lists the built-in controllers of the machine. Click the controller name to get information for the controller (see Figure 5-75).
455
b. Disks: This subtree lists the number of disks that you have attached to your computer (Figure 5-76).
Click one of the disk definitions to get more information about the disk (Figure 5-76).
456
Five tabs appear: General: This tab displays information about the disk and allocations on the disk. Paths: This tab shows how the disk is seen from the operating systems point of view. Latest Probe: This tab contains information gathered during the last probe, such as the physical characteristics of the disk (RPM, sector size, heads, and cylinders), defects, and errors detected. Probe History: This tab shows all of the probe jobs that were run for this machine since the machines installation. LUN Definition: If the CIMOM agent has been configured, the disk subsystem reports its LUN configuration.
457
c. Volume Groups: This subtree lists Volume Groups (for UNIX only). Click the Volume Group to display details. You can get additional information about the disks that construct the Volume Group and the filesystem on the Volume Group (Figure 5-78).
d. Filesystems or Logical Volumes: This subtree lists the filesystems and logical volumes on the selected computer, as shown in Figure 5-79 on page 459. Two tabs are available: Filesystems: This tab shows you the information about the filesystem, such as capacity and number of inodes, and the scan jobs and probe jobs that are run for the selected computer.
458
Logical Volumes: This tab shows us the volume, which constructs the filesystem, as shown in Figure 5-80.
459
e. Exports or Shares: This subtree lists the directories that are shared, as shown in Figure 5-81.
460
f. Monitored Directories: To view a report on a directory that you are monitoring, expand the Monitored Directories node on the Navigation Tree and click the directory for which you want to see details (Figure 5-82).
461
By Hypervisor
In the latest version of TPC, the asset report for VMware ESX Servers is enabled. This selection lists the configured VMware ESX Servers and their respective Virtual Machines, as shown in Figure 5-83. We cover the VMware ESX Server reports in 5.8, VMware ESX Server support on page 529.
By OS Type
Computers are grouped into operating system type. The following operating system types are available: Windows NT Windows Microsoft Cluster Resource Group Solaris Linux Hewlett-Packard UNIX (HP-UX) AIX HACMP Cluster Resource Group NetWare Network Appliance Other NAS
462
IBM storage area network (SAN) FileSystem VMware ESX To get the assets for one of the Windows machines, do these steps: 1. Select Data Manager Reporting Assets By OS Type. 2. The list of OS types displays. We selected Windows in order to view the list of Windows machines in the environment, as shown in Figure 5-84. You can drill down to see additional information, such as Controllers, Disks, Filesystems, Exports or Shares, and Monitored Directories.
463
3. Click one of the machines to get information about the computer that has a Windows operating system running, as shown in Figure 5-85. You can drill down to the sub menus to see the detailed information about Controllers, Disks, Filesystem or Logical Volumes, Exported directories, and Monitored directories.
By Storage Subsystem
This selection lists the available storage subsystems in the environment. For example, you can view the following information (Figure 5-86 on page 465): For an ESS subsystem, you can view disk groups, volume spaces, disks, and LUNs. For DS6000 and DS8000, you can view Disks, ArraySite, Ranks, Extendpools, and Volumes For a SAN Volume Controller (SVC), you can view managed disk groups, managed disks, and virtual disks.
464
For IBM FAStT and HP StorageWorks, you can see storage pools, disks, and LUNs. For Hitachi Data Systems, you can see storage pools and LUNs.
With IBM TotalStorage Productivity Center V3.3.2, we can see the Space-Efficient Volumes reports for DS8000, but we cannot use Disk Manager to create or delete Space-efficient Volumes.
465
To see the reports for Space-efficient volumes, select Data Manager Reporting Assets By Storage Subsystem and select the Space-efficient volume under the DS8000 storage subsystem. This will show you the details of the Space-efficient Volume in the content pane (Figure 5-87).
System-wide
This selection allows you to view the assets on the entire environment. The data is aggregated and shown as a system-wide report. For example, the following subtrees are available, as shown in Figure 5-88 on page 467.
466
Agents
The System-wide Agents report enables you to track and monitor the Data agents deployed in your storage environment. This report enables you to: View information about the agents deployed in your environment. Perform actions against one or more agents shown in the report. To get the report for agents, use the following steps: 1. Select Data Manager Reporting Assets System-wide Agents. The Report Generation window appears.
467
2. Select the columns that you want included and excluded and click Generate Reports. TotalStorage Productivity Center for Data lists all of the agents that are registered in addition to information about the agents, such as Agent Status, OS Type, Version, Host ID, Host Address, Last Update, Time Zone, Connection Errors, Consecutive Errors, and CPU Architecture (Figure 5-89).
You can click the Magnifying glass icon next to each agent to get more detailed information.
Computers
To create the report for computers, follow these steps: 1. Select Data Manager Reporting Assets System-wide Computers. The Report Generation window appears. 2. Select the columns that you want included and excluded and click Generate Report. TotalStorage Productivity Center for Data shows you all of the computers, as shown in Figure 5-90.
468
3. Clicking the magnifying glass icon shows you a detailed report for the computer in addition to the following information: Network Address IP Address OS Type OS Version Time Zone Manufacturer Model Serial Number Processor Type Processor Speed Processor Count RAM Swap Space Disk Capacity Unallocated Disk Space Filesystem Free space Last Boot Time Last Probe Time Last Probe Status Discovered Time CPU Architecture
Disks
To get the report for disks, follow these steps: 1. Select Data Manager Reporting Assets System-wide Disks. The Report Generation window appears. 2. Select the columns that you want included and excluded and click Generate Report.
469
3. TotalStorage Productivity Center for Data lists all of the disks with additional information about the disks, such as Path, Manufacturer, Model, Storage System, RPM, Capacity, and Number of Defects (Figure 5-91).
In addition to the above reports, we can also see some other reports in the System wide reports. We can generate them in the same way as the above reports. Here is the list of those reports: Storage Subsystems Reports Unmanaged Virtual Machine Reports Virtual Machines with no VMware Agent installed FileSystem or Logical Volumes Reports LUNs Reports Exports and Shares Reports
470
5.4.3 Availability
TotalStorage Productivity Center for Data can keep track of all agents availability for the agents that are registered on it. Uptime and statistics regarding sending and receiving signals are saved and can be seen as a report. Two subcategories are available: Ping and Computer Uptime. To get a ping statistic for one of the machines, follow these steps: 1. Select Data Manager Reporting Availability Ping. 2. Five subcategories can be selected: a. b. c. d. e. By Cluster By Computer By Computer Group By Domain Network-wide
3. For example, click By Computer. The Selection window appears, as shown in Figure 5-92. We can limit the report for a certain date range or certain computers. If nothing is selected, the report works for all date ranges and for all of the computers in the environment. 4. Click Generate Report.
To get a Computer Uptime report for one of the machines: 1. Select Data Manager Reporting Availability Computer Uptime.
471
2. Five subcategories can be selected: a. b. c. d. e. By Cluster By Computer By Computer Group By Domain Network-wide
3. For example, click By Computer. See Figure 5-93. Ping by cluster can be used to ping Microsoft Cluster and HACMP on AIX. 4. Click Generate Report. 5. The report displays the availability of the computer and how many times it has been booted.
5.4.4 Capacity
Capacity information is also available in the repository. TotalStorage Productivity Center for Data can report this value again by several options, such as by disk, by storage subsystem, by cluster, by computer, by computer group, by domain, and network-wide. Four subcategories are available: Disk Capacity Filesystem Capacity Filesystem Used space Filesystem Free space For example, to get the disk capacity for a network-wide view, follow these steps: 1. Select Data Manager Reporting Capacity Disk Capacity. 2. Click Network-wide and the Report generation window appears. 3. Click Generate Report to create the report for Network-wide. 472
4. One line displays for Network-wide. Click the Pie chart icon to view the report in chart format, as shown in Figure 5-94.
5. To focus on the disk capacity for each computer, click the Network-wide tab and click the magnifying glass located to the left of the line. The Disk Capacity report for all of the computers displays, as shown in Figure 5-95.
473
6. To get details for an individual row, click the magnifying glass icon to the left of the row, as shown in Figure 5-96.
7. Note that you can get more details about the disk on the selected computer by accessing the TotalStorage Productivity Center for Data report, which you can do by selecting Data Manager Reporting Asset By Computer computer name Disks. 8. Right-click and select Chart: All rows, as shown in Figure 5-97.
The line graph to chart all of the disk capacity by computer is shown in Figure 5-98 on page 475.
474
To get network-wide filesystem capacity, follow these steps: 1. Select Data Manager Reporting Capacity Filesystem Capacity. 2. Click Network-wide. The Report Generation window appears. 3. Click Generate Report to create the report for network-wide. 4. One line displays for network-wide. The report shows the following information: Capacity Percent Used Space Used Space Free Space Filecount Directory Count Percent Used Inodes Free Inodes
5. Click the magnifying glass icon to see all of the computers in the environment.
475
6. Right-click and select Chart space usage for all. 7. You get a report of Used Space and Free Space of two computers at a time. 8. Right-click and select Customize this chart to change the chart type or the number of computers shown at a time, as shown in Figure 5-99.
A history report can be important for you to predict the future of your capacity depending on current trends. To get a history report: 1. Select Data Manager Reporting Capacity Filesystem Used Space. 2. Click By Computer. The Report generation window appears. 3. Click the magnifying glass icon next to one of the computers. 4. Right-click and select History Chart: Used Space for selected. The chart shown in Figure 5-100 on page 477 displays, starting from the first scan to the last scan.
476
5.4.5 Usage
Usage reporting enables you to report on the usage and growth of the consumption of your storage. TotalStorage Productivity Center for Data can report this value again through several options, such as by disk, by storage subsystem, by cluster, by computer, by computer group, by domain, and network-wide.
477
Here are the categories that are available under Usage Reports. Figure 5-101 shows the navigation path under the Usage Reports. Access Load Files Directories Users OS User Groups
We have already seen several reports in 5.2.1, Predefined reports under the My Reports node on page 392. In this section, we show several reports that were not mentioned in the My Reports section. To get a Creation Time report, do these steps: 1. Select Data Manager Reporting Usage Access Load Creation Time. 2. Click Network-wide. 3. The Report generation window appears. Select the profile. 4. Click Generate Report to create the report for network-wide. 5. One line of the report tells us the number of files that were created in: Less than 1 day Within 1 week Within 1 month 478
Deployment Guide Series: IBM TotalStorage Productivity Center for Data
Between 1 and 2 months Within 1 year More than 1 year 6. Click the pie chart icon to view the report in pie chart format, as shown in Figure 5-102.
You can view the usage reports for files also, which gives you the details for the number of files and their occupied space on the basis of file type. To get a File Types report, do these steps: 1. Select Data Manager Reporting Usage Files File Types. 2. Click Group by File Type and Network-wide. 3. The Report generation window appears. Select the profile. 4. Click Generate Report to create the report for network-wide. 5. This lists all of the file types within all computers. 6. To select specific file types, click Selection.
479
7. File types appear in a pop-up window. Put a check mark on the file types that you want to include in the report (for example, check only the following file types: avi, bmp, db2, db, jpg, and zip.) 8. The report shows the number of files, Type Description, Total Size of the file, and percentage of used space (Figure 5-103).
9. Click the magnifying glass icon to the left of the line in Figure 5-103 to display the computers that have the selected file types, for example, computers that have *.jpg files (Figure 5-104).
To get a Duplicate File report: 1. Select Data Manager Reporting Usage Files Duplicate Files. 2. Click By computer. The Report generation window appears. 3. To select the computer, click Selection. Select only one computer.
480
4. This report lists duplicate files for the selected computer (Figure 5-105).
481
5. Click the magnifying glass icon in Figure 5-105 on page 481 to get details about a selected file (Figure 5-106).
6. You can automatically trigger a Tivoli Storage Manager backup and then delete the file if you want. To trigger a backup this way in the duplicate file list window, highlight the file, right-click, and select Create a new archive/backup job.
5.4.7 Backup
Backup reporting allows us to see the files that are most at risk and the files that have been modified but not backed up. At this list, we can run backup jobs against the files, and, therefore, we can be proactive about saving the files.
482
This node of the explorer view has the following subnodes: Most at Risk Files Modified Files not Backed Up Backup Storage Requirements Use the following steps to get the report for the Most at Risk Files: 1. Select Data Manager Reporting Backup Most At Risk Files. 2. Click Network-wide. 3. The Report generation window appears. Select the profile. 4. Click Generate Report to create the report for network-wide. 5. The file list displays. It is sorted by Modification Time, as shown in Figure 5-107.
6. Select a file or files from the list, right-click, and select Create a new archive/backup or Add an existing archive/backup job.
483
7. The Create File Archive/Backup Action window appears. Select the backup type, such as Archive, Selective backup, or Incremental backup (Figure 5-109 on page 485).
8. Click the When to Run tab to schedule the backup job. 9. Press Ctrl+s to save the job. You can follow the status of the job by selecting Data Manager Policy Management Archive/Backup job-name date-time. If you decide to back up or archive the files to Tivoli Storage Manager, you might need to know how much storage is needed by the Tivoli Storage Manager server to back up the selected files. By having this information, you can calculate the time needed to back up the files or calculate the disk or tape storage needed for the files. TotalStorage Productivity Center for Data can also give you this information. Backup Storage requirement is an excellent tool for planing the storage pool or tape requirement for your backup environment. It has the ability to generate multiple reports, such as Full backup and Incremental. These reports can be generated by Directory, by Directory Group, by Filesystem, by Filesystem Group, by Cluster, by Computer, by Computer Group, by Domain and Network Wide. These reports allow you to see, for any of these levels, how much data would need to be backed up for any of these desired time intervals. This is useful for determining backup sizing and can be used to determine appropriate backup groups and setting the timing of your backups. To obtain the total size of the backup, follow these steps: 1. Select Data Manager Reporting Backup Backup Storage Requirements Full Backup Size. 2. Click Network-wide.
484
3. The Report generation window appears. Select the profile. 4. Click Generate Report to create the report for network-wide. 5. One line of the report tells us the total backup size (Total Size) and the total number of files to back up (File Count), as shown in Figure 5-109.
6. You can click the magnifying glass icon to display a report for each computer, as shown in Figure 5-110.
485
7. You can click the magnifying glass icon again to get the filesystem list for each computer, as shown in Figure 5-111.
487
2. In Figure 5-113, select the magnifying glass icon that is located to the left of the line TPC for Data - Databases. Figure 5-114 appears.
488
3. In Figure 5-114 on page 488, select the RDBMS Logins tab, and then select Add New. Configure the login properties for your database instance on the target server, as shown in Figure 5-115.
4. After you click Save in Figure 5-115 to complete this task, you get a success message, as shown in Figure 5-116. You will now see that the new database host and information are listed after the configuration.
489
490
2. You can add Instances and use the arrows to move the instances to the Current Selections column. In Figure 5-118, select File Save and give the probe a name. Select OK, and the probe will be submitted.
491
492
4. Next, we need to create a scan to gather more detailed information about the database. Select Data Manager for Databases Monitoring Scans. Select the default scan and select Run Now, as shown in Figure 5-120.
493
5. Monitor the scan job until it completes (Figure 5-122 on page 495).
494
3. Click Generate Report to create the report By Computer. The report displays the capacity for each computer (Figure 5-122).
495
4. Click the magnifying glass icon to view a selected server, as shown in Figure 5-123.
5. Now, drill down on the selected computer for instance information (Figure 5-124).
6. If you click the magnifying glass icon, you can get a listing of the Database Files, as shown in Figure 5-126 on page 498.
496
497
498
499
5. Now, click the line graph icon, and you see the Usage graph report (Figure 5-128).
5.6 Topology
The Topology Viewer provides a graphical representation of the physical and logical resources (for example, computers, fabrics, storage subsystem, and so on) that have been discovered in your storage environment by TotalStorage Productivity Center. In addition, the Topology Viewer depicts the relationships among resources (for example, the disks comprising a particular storage subsystem). Detailed tabular information (for example, attributes of a disk) is also provided. With all the information that the Topology Viewer provides, you can more quickly and easily monitor and troubleshoot your storage environment and perform critical storage-management tasks. The overall goal of the Topology Viewer is to provide a central location to view a storage environment, quickly monitor and troubleshoot problems, and gain access to additional tasks and functions within the TotalStorage Productivity Center graphical user interface (GUI) without users losing their orientation to the environment. This kind of flexibility through the Topology Viewer UI displays better cognitive mapping between the entities within the environment, and
500
provides data about entities and access to additional tasks and functionality associated with the current environmental view and the user's role. The Topology Viewer uses the TotalStorage Productivity Center database as the central repository for all data it displays. It actually reads the data in user-defined intervals from the database and, if necessary, updates the displayed information automatically. The Topology Viewer was introduced in TotalStorage Productivity Center Version 3.1 and has been significantly enhanced in Version 3.3 and later. To launch the topology viewer, select IBM TotalStorage Productivity Center Topology (Figure 5-129). This will show you a high level view of all the components in your environment (Figure 5-129). By clicking an individual component, you can see more details for that component.
501
The new features that were introduced in TotalStorage Productivity Center for Data for the Topology Viewer are: Pin list persistence Topology Viewer link to reports and alerts Context Sensitive Reporting and Data Path Explorer Capacity GUI navigation tree enhancements
502
3. Figure 5-131 on page 504 shows the entities that we have pinned in the Topology Viewer Overview window.
503
In general, note that pinning provides a direct path to look at an entity in detail just by double-clicking it. Notice that in a collapsed group, the pinned entities are displayed (Figure 5-131). In an expanded group, pinning is shown on each pinned entity.
504
Link to alerts
From the Topology Viewer, you might notice that there is a red exclamation point character (!) shown beside an entity or in the group title, which indicates that there are alerts for this entity or entities within the same group. You can hover your mouse over the red exclamation point, and it shows you the number of alerts that are now open for the selected entities (Figure 5-132).
505
Use the following steps to launch alerts from the Topology Viewer: 1. Right-click the entity and choose Show <entity type> Alerts (in our example, we are looking at the Switches Group, so the option is Show Computer Alerts), as shown in Figure 5-133.
2. The TotalStorage Productivity Center for Data GUI then launches the related alert view, as shown in Figure 5-134 on page 507. You can look at the alert and then choose Clear to acknowledge the alert or Delete to delete the alert if you do not need the information any longer.
506
Link to reports
In the Topology View, from the L0-L2 graphic view of Computers and Storage classes, you can link to reports that reflect the entities from which you choose. This function is extremely convenient when you look at an entity or a certain group of entities, and you want to view a report to see more information.
507
Here is a example of creating a report from the Computer group graphic view: 1. Select the title of the Computer group, right-click, and select Reports from the pop-up context menu, as shown in Figure 5-135. Note: Do not right-click the computer entity, because then the report information will only reflect that computer.
508
2. The pop-up window displayed shows the available reports (related to the selected entity) that you can generate. In our example, we select Data Manager Capacity Filesystem Used Space By Computer, and click Create Report (see Figure 5-136).
509
3. TotalStorage Productivity Center GUI then brings up the TotalStorage Productivity Center Generate Report window (Figure 5-137).
Figure 5-137 Report navigation to Generate Report for selected group entity
4. Select the columns that you want included or excluded and click Generate Report. TotalStorage Productivity Center displays a Filesystem Used Space report for the selected computer group in the selected Topology Viewer, as shown in Figure 5-138 on page 511.
510
511
You must have an in-band or out-of-band Fabric agent. Note that in an out-of-band Fabric agents only environment, the out-of-band agents need to be configured for all of the switches in a fabric. A CIM Agent for the SVC is needed to view data paths involving the SVC. No data paths show if any one of the previous agents is not configured. For a zone overlay with SMI-S compatible SAN switches, you do not need CIMOMs. You need an in-band Fabric agent for non-SMI-S compatible SAN switches. For a performance overlay, you need to configure switch and subsystem performance monitors. Only the subsystem device driver (SDD) is supported for Multi-path driver on all OS platforms. On Windows, SDD V1.6.1 or greater is needed. To launch the Data Path Explorer, in Topology Viewer, select one or more hosts, subsystems, disks, volumes, or Mdisks and click the Data Path Explorer shortcut in the MiniMap tool (see Figure 5-139).
Note: In order to view the Data Path Explorer for a host, you must have the Data agent and an out-of-band Fabric agent on the SAN or SIM-S configured on the SAN Switch to which the host is connected.
512
The Data Path Explorer view for hosts is shown in Figure 5-140. From this view, you can see how the host volumes connect through the fabric to the storage subsystem.
513
The Data Path Explorer view for a subsystem is shown in Figure 5-141. If the subsystem is an SVC, you can see from this view how the SVC MDisks connect through the fabric to the SVCs back-end storage subsystem. If the subsystem is not an SVC, you can see from this view how the subsystem connects to its hosts.
The Data Path Explorer view for an MDisk is shown in Figure 5-142 on page 515. From this view, you can see how the MDisk comes from its back-end subsystem.
514
The Data Path Explorer view for a volume is shown in Figure 5-143. From this view, you can see how the volume from the subsystem connects to an SVC or hosts.
515
516
Fabric agents (Inband and Out of Band), CIMOM agents, and VM servers (VMware). We recommend that each subordinate server monitors no more than 1200 unique data sources. This number includes Data agents, Fabric agents (Inband and Out of Band), CIMOM agents, and VM servers (VMware). Once this threshold has been met for a server, a new server should be deployed and all new agents pointed to it. You must have TotalStorage Productivity Center superuser or IBM TotalStorage Productivity Center administrator authority to perform administrative operations such as adding a subordinate server to the master server list to monitor. After upgrading to TotalStorage Productivity Center V3.3 or later from a previous version of the application, you must run probes against a master server's monitored storage assets to have information about those assets appear in the Navigation Tree IBM TotalStorage Productivity Center Rollup Reports path. When you add a subordinate server to the master server list, you must provide the host authentication password of the subordinate server to the master server. The host authentication password is checked each time the master server is probed. This host authentication password is entered when installing TotalStorage Productivity Center. Rolled up data from TotalStorage Productivity Center subordinate servers is stored in new tables in the master TotalStorage Productivity Center server. Otherwise, all of the existing TotalStorage Productivity Center reports need to be modified if rollup data is put into the existing T_RES_*** tables. Using TotalStorage Productivity Center V3.3 with new table definitions allows you to create, store, and retrieve rolled up data.
517
In this section, we describe: How to define subordinate TotalStorage Productivity Center servers to the master TotalStorage Productivity Center server. How to combine reports for multiple TotalStorage Productivity Center servers into an enterprise-wide Rollup Report, which gives the client a complete view of its environment.
the following steps on the master TotalStorage Productivity Center server to add a subordinate TotalStorage Productivity Center server: 1. Expand Administrative Services Data Sources in the Navigation Tree. 2. Click TPC Servers. 3. Click Add TPC Server. Figure 5-145 shows the result of performing these steps.
After the Add TPC Server window appears, enter: A host name or IP address of the TPC server. We recommend that you enter a Fully Qualified DNS Name. A host Device server port. The default port is 9550. The host authentication password (which is the TotalStorage Productivity Center host authentication password of the Device server). Optionally, enter a display name.
519
Optionally, enter a description Select Test TPC Server connectivity before adding in the Add TPC Server window for a subordinate TotalStorage Productivity Center server that is up and running and whose authentication data matches the data of the data provided in the Add TPC Server window. Click Save on the Add TPC Server window.
520
521
To probe subordinate TPC servers, you must create a probe definition. By default, all of the newly registered subordinate servers are added in the default TPC server probe definition. Prior to scheduling a TPC Server probe, verify that at least one subordinate TPC server with data is being monitored by the master TPC server. To schedule a TPC server probe, perform the following steps from the master TPC server: 1. From the main Navigation Tree pane, select IBM TotalStorage Productivity Center Monitoring TPC Server Probes. 2. Under the What to Probe tab, select All TPC Servers, which is depicted in Figure 5-147, and all of the resources will be probed. 3. You also can select a specific TPC server to probe, as well as the class of information to pull from the probed servers (subsystem, fabric, computers, clusters, tapes, or databases). This information is stored in the master servers local database.
The results of a successful TPC subordinate probe are shown in Figure 5-148 on page 523, depending the number of TPC subordinate servers selected and the data gathered.
522
523
Database Capacity: These reports provide storage metrics related to the storage capacity of the RDBMS in your environment, including Oracle, SQL Server, Sybase, and DB2 UDB.
524
Use the Selection window to select the profile to use when generating a report and determine which columns appear within the report. Click Selection to select the objects on which you want to report from the Select Resources window (Figure 5-150). Click OK.
525
Click Filter to further filter the objects that appear in a report. Filters enable you to apply general rules to the report based on the rows in that report. Figure 5-151 illustrates the Filter window.
Click Generate Report. A new tab will be added to the tab window representing the report that you generated. Reports are tabular in format and are comprised of rows and columns. You can scroll the report up and down and to the right and left to view the entire report. Use the View menu to hide or show the Navigation Tree to increase the viewable area of the report or drag the divider bar in the middle of the window back and forth to reallocate the amount of space that is given each pane. Figure 5-152 on page 527 is an example of a Storage Subsystem Capacity Rollup Report.
526
527
Figure 5-153 illustrates the window used to generate the Asset Information Report by Computer. Notice the information in the right-most column; this information will be displayed in the generated report.
Figure 5-154 on page 529 shows an Agent Asset Rollup report by agents.
528
These two examples illustrate how you can roll up network-wide summary metrics from multiple TPC servers and report on their storage environment from a network-wide perspective.
529
As shown in Figure 5-155, the data flow between the VMware environment and the TotalStorage Productivity Center consists of the two connections: the connection of the TotalStorage Productivity Center to the VMware Host Agent of the VMware ESX server through the new VMware VI Data Source, and the connection of the TotalStorage Productivity Center Data agents residing in the VMware virtual machines inside the VMware ESX server.
Figure 5-155 VMware ESX Server communication with TotalStorage Productivity Center
530
Figure 5-156 Topology Viewer Overview window showing hypervisor and virtual machines
531
The L0 overview of Computers shows all computers, virtual computers, and hypervisors (see Figure 5-157). Notice the computer type column on the bottom of the window. Double-click your hypervisor to get to the L2 overview of your hypervisor computer.
532
The L2 Computer window shows detailed information about your hypervisor. You can see information that is separated in the Device, Virtual Computers, and Connectivity tabs. Return to the previous window (Figure 5-158) and double-click one of your virtual computers for the L2 view of a virtual computer.
533
The Virtual Computer L2 Overview shows detailed information about Device and Connectivity characteristics (Figure 5-159). The Device tab shows additional controller and virtual machine (VM) disks information. The Connectivity tab shows additional switches information.
534
535
536
Expand the ESX Server menu in the Navigation Tree to see the details about Virtual Machines, Controllers, Disks and Filesystem, or Logical Volume Details for that ESX Server (Figure 5-162).
Figure 5-162 VMs, Controllers, Disks and FileSystem details menu for ESX Server
537
To see Virtual Machines details, expand the Virtual Machines menu (Figure 5-163). This will show you all the Virtual Machines on the ESX Server, including the one on which a Data Agent is not installed. We will discuss the Virtual Machine reports in more detail in Reports for Virtual Machines on page 542.
538
To see the Controllers details for ESX Server, expand the Controller menu. This will list all the controllers on the ESX Server (Figure 5-164). You can see the details of individual controller by expanding the corresponding menu.
539
Expand the Disks sub-menu to get the list of all the disks on ESX Server (Figure 5-165). It will show you the list of all the disks on the ESX Server, including the local disks as well as the disks from storage subsystem.
540
The right side control pane shows the details about each of the disks. It shows the General Information, Path details, Latest Probe, and Probe History Details for all of the disks and LUN Definition for the disks that are mapped from storage subsystem. LUN Definition or LUN Correlation gives you the information about disk to LUN mapping. The information includes LUN Name, LUN WWN, and Storage SubSystem Details (Figure 5-166). By using LUN Definition, you can discover which disk is mapped to which Storage and LUN.
541
Expand the Filesystem or Logical Volume sub-menu for the ESX Server to see the list of all the filesystems or logical volume on ESX Server (Figure 5-167). The right side control pane shows the details of the filesystem, including filesystem type, mount point, capacity and usage details, and probe and discovery details.
542
For the Virtual Machines on which Data agent is not installed, only limited information is displayed (Figure 5-168). The information that is displayed is the Virtual Machine name, Hypervisor name, VM Configuration File path, OS Details, Processor Count, and RAM size.
Figure 5-168 Information about Virtual Machine on which data agent is not installed
543
More detailed reports can be seen for Virtual Machines on which a Data agent is installed. Upon clicking the Virtual Machine name, the right hand control pane gives information about the Virtual Machine, such as VM name, Hypervisor name, VM Configuration file path, Network Address details, hardware details, operating system details, disk capacity details, and probe and discovery details (see Figure 5-169).
Figure 5-169 Detail about Virtual Machine on which Data agent is installed
544
You can also see the Controllers, Disks, Filesystem or Logical Volume, Exports or Shares and Monitored Directories details about the Virtual Machine on which the Data agent is installed. Expand the Virtual Machine menu to get to these details (Figure 5-170).
Figure 5-170 Controllers, Disks, FS or LV, Exports and Monitored Directories details for a VM
545
Expand the Controllers sub menu for the VM to get the list of controllers. Click the controller to get the corresponding details (Figure 5-171).
Expand the Disks submenu of the VM to get the details about the disks on the VM. It will show you the list of all the disks on the Virtual Machine, including the disks mapped from ESX Servers local Datastore as well as the disks from storage subsystem (see Figure 5-172 on page 547). The right side control pane shows the details about each of the disks. It shows General Information, Path details, Latest Probe and Probe History Details, Mapping to Hypervisor for all of the disks, and LUN Definition for the disks that are mapped from the storage subsystem.
546
547
Mapping by Hypervisor shows disk mapping details from VM to hypervisor. It shows Disk name on VM, VM and Hypervisor name, Mapping type, VMDK file name on Hypervisor, and disk name on Hypervisor, as shown in Figure 5-173.
548
LUN Definition or LUN Correlation gives you details about which disk is mapped to which LUN. The information includes LUN Name, LUN WWN, and Storage SubSystem Details, as shown in Figure 5-174. When using LUN Definition, you can discover which disk is mapped to which Storage and LUN.
549
Expand the Filesystem or Logical Volumes sub-menu for the VM to obtain the details of the filesystems, as shown in Figure 5-175. The right side control pane shows the details of the filesystem, such as filesystem type, mount point, capacity and usage details, probe, and discovery details.
550
551
Select the column that you want to select and click Generate Report. A Filesystem Capacity report is generated (see Figure 5-177). The report shows the filesystem details of all the VMs on which a Data agent is installed and for the VMware ESX Server.
Note: You must probe both the ESX Server and the Data agent on the virtual machines before you can generate accurate reports for disk and filesystem capacity. For example, you have an ESX Server that has 100 GB, and 60 GB are allocated to the virtual machine. The virtual machine uses 5 GB of space. Both the ESX Server (H1) and the virtual machine (VC1) have been probed. You also have a physical computer (PC1) that has been probed. The total capacity for the filesystem or disk capacity row includes everything, including virtualized disks and virtual machines, as well as non-virtualized disks and machines.
552
553
4. To display the versions of both the Agent Manager and Agent Recovery Service, run the following command: For AIX, Linux, and UNIX: GetAMInfo.sh For Windows (see Figure 5-178): GetAMInfo.bat
554
A useful example of using the HealthCheck command is to display the AgentManager configuration and to verify that the Common agent password that you are using is still valid: For Windows: healthcheck -registrationPw changeMe For UNIX: ./healthcheck.sh -registrationPw changeMe where changeMe is the password that you are checking.
The LogCollector command gathers the logs and other information needed to debug problems with the Agent Manager. When you run LogCollector, it creates the LogCollector.zip file, which is located in the root directory where the Agent
555
Manager is installed. This command must be run from the machine on which the Agent Manager is installed. The files are: LogCollector.sh: This script runs the LogCollector command on UNIX and Linux systems. LogCollector.bat: This script runs the LogCollector command on Windows systems. The script calls the LogCollector.jar file, which is a JAR file that contains the Java code for the command.
556
On UNIX systems: a. Change to the Common agent installation directory: cd <common_agent_install_directory> b. Run the following command to change the agent registration password: encryptPwdInConfFile.sh <agent_registration_password> The variable <agent_registration_password> is the new agent registration password. 5. Restart the Common agent.
557
The endpoint.properties file contains address references to hosts performing various functions. Update these addresses (or host names) to point to the Agent Manager. When the Common agent is installed, the installation process will put in the IP addresses (not host names): AgentConfiguration.Host= CertManagement.Host= AgentQuery.Host= Registration.Host= Registration.domain= Registration.Server.Host= AgentManagerQuery.Host= Config.Server.Host= There are other entries needed to connect to the Agent Manager. You do not need to change these entries from the default values. If you want to validate these entries, you will find them in the Agent Manager configuration files. The parameters are: Registration.Server.Port=<new_registration_server_port_number> Registration.Server.ContextRoot=<new_registration_server_context_roo t> Registration.domain= 3. Delete or remove the certificate files from the Common agent ca/cert directory. As a precaution, create a cert.bak directory and copy the contents of the ca/cert directory to the cert.bak directory. 4. Update the password (if it differs between the Agent Managers). The command is: <common_agent_install_directory>\jre\bin\java -cp lib\ep_install.jar; lib\ep_common.jar com.tivoli.agent.install.EncrPwdInConfFile Config\endpoint.properties Registration.Server.PW <password> 5. Move or delete the contents of the <common_agent_install_directory>\logs subdirectory. 6. Reset the tivguid if you want, but this reset normally is not needed. 7. Restart the Common agent service: For Windows: To start the services on Windows, select Start Control Panel Administrative Tools Services. Start IBM Tivoli Common agent <directory>. For UNIX or Linux: Go to the installed directory and issue this command: /opt/IBM/TPC/ca/endpoint.sh start You see the ports in use and a message in <common_agent_install_directory>\logs\msgAgent.log that shows the agent connecting to the new Agent Manager and registering successfully. The log ends with the standard ready for automated e-business message. You also can see new certificate files in the /cert subdirectory.
558
559
2. Run the repocopy.bat or repocopy.sh command. A window (Figure 5-180) appears. Select Export data from repository tables to export your existing repository data into a comma-delimited file.
a. Click Next. For exporting data, IBM TotalStorage Productivity Center processes the repository table into the comma-delimited file that you specify and places it into a file named <tablename>.txt (Figure 5-181). Click Next to continue.
560
3. The Connection Properties window displays. In this step, IBM TotalStorage Productivity Center reads the server.config file and determines your current repository and the information for accessing the database. The information detected in the server.config file is displayed in the Connection Properties window within the following fields: Database Types, User name, Password, Driver Class, Driver URL, Database, DB Creator, and Classpath (Figure 5-182). Click Finish.
4. The window shown in Figure 5-183 appears. Click Run to start the Export.
561
6. The repocopy utility also has a DOS window running in the background, which shows the progress of the Export function (Figure 5-185 on page 563).
562
563
564
Appendix A.
Worksheets
This appendix contains worksheets that are meant for you to use during the planning and the installation of the IBM TotalStorage Productivity Center. The worksheets are meant to be examples. Therefore, you can decide whether you need to use them, for example, if you already have all or most of the information collected somewhere. If the tables are too small for your handwriting, or you want to store the information in an electronic format, simply use a word processor or spreadsheet application and, using our examples as a guide, create your own installation worksheets. This appendix contains the following worksheets: User IDs and passwords
565
Server information
Table A-1 contains detailed information about the servers that comprise the TotalStorage Productivity Center environment.
Table A-1 Productivity Center server Server Machine Host name IP address ____.____.____.____ Configuration information
In Table A-2, simply mark whether a manager or a component will be installed on this machine.
Table A-2 Managers/components installed Manager/component Productivity Center for Disk Productivity Center for Replication Productivity Center for Fabric Productivity Center for Data Tivoli Agent Manager DB2 Installed (y/n)?
566
Appendix A. Worksheets
567
This is the user ID and password required by the Device server and Data server to register with the Agent Manager. You must specify this user ID and password when you install the Device server or Data server. For information about how to change the user ID and password, see Changing the registration password for a resource manager in IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774. This is the user ID and password required by the Device server to communicate with embedded WebSphere. Embedded WebSphere runs as a Windows Service. The Windows Service runs under the authority of this user ID and password. This user ID and password is only used when you install the Device server. This account and password is valid for Windows only and lets the agent run under this service account.
If this user ID and password does not exist, these will be created at installation time. When you install the IBM TotalStorage Productivity Center agent, you will be able to specify a domain name, which validates the account and password.
agentTrust.jks Enter the user IDs and password that you used during the installation in Table A-5. Depending on the selected managers and components, some of the lines are not used for this machine.
Table A-5 User IDs used on this machine Element Default/ recommended user ID db2admina Enter user ID Enter password
568
Element
Enter user ID
Enter password
DB2 Instance Owner DB2 Fenced User Resource Manager Common Agent Common Agent TotalStorage Productivity Center universal user IBM WebSphere Host Authentication
c c
a. This account can have any name you choose. b. This account name cannot be changed during the installation.
Appendix A. Worksheets
569
570
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.
Online resources
These Web sites and URLs are also relevant as further information sources: TotalStorage Productivity Center Version 3 Release 3 Supported Product List: http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002800
571
TotalStorage Productivity Center Version 3 Release 3: Supported Products List - all vendors http://www-1.ibm.com/support/docview.wss?rs=1133&context=SS8JB5&cont ext=SSWQP2&dc=DB500&q1=HP+XP&uid=ssg1S1002824&loc=en_US&cs=utf-8&lan g=en TotalStorage Productivity Center Version 3 Release 3 Platform Support: Agents, CLI, and GUI http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002814 TotalStorage Productivity Center Version 3 Release 3 Platform Support: Managed Database Support http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813 TotalStorage Productivity Center support Web site http://www.ibm.com/servers/storage/support/software/tpc IBM Redbooks publications http://www.redbooks.ibm.com/
572
Index
A
Access Time Summary report 394 Active Directory 59 Add the root user to the DB2 instance group 190 administrative rights DB2 user 95 administrator type users 59 advanced copy services 5 advanced provisioning 19 Agent install via GUI 64 remote install 64 agent 10, 22 information 388 agent communication ports 295 agent component log 386 agent deployment 288 Common Agent logs 324 interactive installation 289 local installation 288 log files 323 remote installation 288 run scripts 294 service 322 silent installation 288 Solaris 10 system 308 unattended (silent) installation 300 agent disk requirements 35 agent information 385 agent install verification 320 Agent Manager certificates 60 change agent ownership 557 database connection 128 default password 145 default user ID 144 healthcheck utility 126 key file 60 reregister agent 556 security certificate 116 server installation 144 server port 9511 144 Agent Manager install graphical installers 173 Agent Manager installation 71, 105 Agent Manager Password 117 Agent Manager repository 45 Agent Manager services host name 111 Agent Manager Toolkit 554 agent recommendations 49 Agent Recovery Service 113 agent registration confirm password 556 agent registration password 60, 85, 118, 277 agent remote installation 306 agent reregistration 556 agent uninstallation procedures 325 agents install path 290 NAS filers 40 agents report 467 agentTrust.jks file 61, 118 AIX install Agent Manager 239 Agent Manager installation 254 Agent Manager password 251 Agent Manager Registration Port, 246 agent registration password 251 certificate authority password 250 certificates 249 create database schema 263 DAS user ID 225 DAS user window 224 database connection type 264 database schema 257 Database User Information 245 DB2 215 DB2 fenced user ID 164, 229 DB2 Fix Pack 170, 235 DB2 instance owner 264 DB2 port 50000 273 DB2 UDB 216 Device server 280 downloaded image 258 installation media 215 keystore file 251
573
NAS discovery 276 root user 190, 238 Schema name field 265 Security roles 274 shut down DB2 environment 171, 236 SNMP community 276 source the DB2 environment 258 su - db2inst1 169, 234 Tivoli Agent Manager 242 Tivoli Agent Manager registry 242 TPCDB 264 unmount install media 235, 256 verify DB2 installation 234 VNC Viewer 216 AIX machine information 35 alert conditions 431 alert disposition 341 alert statistics 429 Alert Triggering Condition 430 alerting 428 facility 24 alerts notification 24 SNMP port 341 architectural overview 18 ARS.version field 127 asset by computer 474 asset reporting reports asset 452 assets By Storage Subsystem 464 System-wide 466 automatic file system extension 10
CIMOM interoperability namespace 66 manually entering CIMOMs 366 CIMOM component log 386 CIMOM configuration 356 CIMOM discovery 360 CIMOM discovery alert 357 CIMOM discovery job 357, 359 CIMOM logins 356 CIMOM logs 368 clients 9 commands netstat -a 71 netstat -an 51 Common agent password verification 555 Common agent port 51 Common agent registration 118 Common agent registration password 295 Common agent service 322 comprehensive reporting 13 computer alerts 429 computer group 418 Computer Uptime report 471 computers report 468 configuring TotalStorage Productivity Center for Data 287 constraints 442 content window 382 create a quota 439 create truststore 348 Custom installation 72, 131 user ID and password rules 80 Custom installation component selection 132 customer support 68
B
backup and archive 404 backup reporting 482 batch report type 411 batch reports 410
D
Data agent 388 install options 317 local uninstall 326 monitored databases 47 remote target 318 remote uninstall 330 scripts 317 uninstall 324 Data agent upgrade 336 data flow 19 Data Manager
C
capacity information 472, 477, 494, 497 CD layout 73 centralized repository 45 Certificate Authority file 60 certificate authority password 85 changing agent configuration 284
574
data retention 369 logfile retention 342 My Reports 393 user defined profile 427 Data Manager node 416 Data Migration Utility 47 Data Path Explorer 511 launch 512 MDisk view 514 data retention 369 Data server port 9549 142 ports 51 Data server component 6, 48 Data Server port 9549 292 Data server service 150 Data Sources 388 Data user levels 58 database creation 133 Database Migration Utility 46 database reporting 372 database repository 45 database support 13 database-managed space 45 databases IBMCDB 45 DataManager 21, 24 operating 380, 553 DataManager for Chargeback 375 DB2 file system ownership 258 DB2 Administration Server 94 DB2 database performance 134, 197 DB2 database sizing 134, 197 DB2 installation 87, 110 administrator group 99 default path 94 verify installation 103 DB2 instance owner user ID 228 DB2 log files 138 DB2 password rules 84 DB2 user account 95 DB2 user and password 133 DB2 user IDs 84 DB2 user rights 84 DB2 window services 104 DB2ADMNS group 110 db2level command 104
db2profile script 173 default database name 45 default installation directory 70, 72 Device server port 9550 142 Device server component 6 Device server port 9550 293 Device Server service 150 directories Exports or Shares 460 directory alerts 433 directory group 419 directory grouping 419 disk capacity Network-wide 473 Disk Capacity Summary report 397 disk report General 457 Latest Probe 457 Paths 457 disk/volume group support 55 disks report 469 display system properties 35 DNS suffix 75 domain name system 75 Duplicate File report 480
E
endpoint configuration file 557 enterprise repository 21 Enterprise Rollup reporting master server 516 Enterprise Server Rollup 516 ESX Server 41 Exports or Shares report 460
F
filesystem 418, 458 alerts 432 extension 10, 54, 447 Filesystem Capacity report 475 filesystem group 418 filesystems supported 54
G
generate a report 398
Index
575
GetAMInfo command 553 groups 418 GUI applet 280 GUI for Web access 151 GUID 78 gunzip command 240
K
key configuration 288 key file for Agent Manager 60 keytool command syntax 349 keytool command 347348
H
HACMP support 16 hardware prerequisites 34 HealthCheck command 554 healthcheck utility 126 historical report 476 history aggregator 353 Host authentication password 143, 312 HTTP connection 24 hypervisor product 12 hypervisors 531
L
Language selection window 130 launch-in-context feature 15 License Agreement window 130 Linux install images 192 Linux install 151 agent manager password 183 agent recovery service 179 agent registration password 183 agent scan 210 certificate authority password 182 Common agent registration password 211 DAS user window 158 database administrator 196 database schema information 197 DB2 installation 151 DB2 instance owner 163 DB2 tools catalog 164 DB2 UDB connection 177 demonstration certificates 181 fenced user window 163 groups command 191 host communication password 206 host name 206 IBMCDB database 177 NAS Discovery Information 209 root user group add 191 run a script 210 SMTP notification 165 start TPC GUI 214 Tivoli Agent Manager 174 verify DB2 installation 169 WebSphere Application Server connection information 178
I
IBM Tivoli Enterprise Console 25 Tivoli Storage Manager 27 IBM TotalStorage Productivity Center for Disk 5 for Fabric 4 for Replication 5 IBMCDB database 110 installation agent installation 63 agent locally 64 Agent Manager 70 electronic image 148 IBM Tivoli Storage Manager 69 instructions 69 user ID privileges 57 user IDs 57 installation licenses 131 integration 24 with IBM products 25 with ITSM 10 IP address 566 IPv6 considerations 42 itcauser 296, 316
J
job
576
Linux space requirements 35 local agent uninstall 326 log files CLI 151 Data server 150 Device server 150 GUI 151 LogCollector for Agent Manager 555 log-file retention 342 logical volumes 459 LUN definition 457
nslookup 62
O
online support 68 operating DataManager 380, 553 operating system type reports 462 operator type users 59 OS user group grouping 421 oslevel command 62 overview 1
M
Microsoft Cluster Server 23, 452 Monitored Directories report 461 monitoring 417 monitors 13 multiple condition alert 432 Multiple disk install window 148 My Reports node 393
P
pin list persistence 502 ping job 421 pinning 502 platforms supported 36 Policy Management 438 Archive/Backup 449 constraints 442 quotas 439, 482 scheduled actions 447 policy-based management 10 ports Data server 51 reserved 72 predefined reports 393 Primary DNS suffix 77 private pin lists 502 privileges for install user ID 57 probe job 413 VMware environment 352 probe setup 490 PROBE_ME file 285 profile creation 426 ps -ef command 322 public communication port 9513 144
N
NAS 12 NAS considerations 39 NAS discovery 276 NAS discovery information 143 NAS environment considerations 39 NAS filers 39 NAS support 23, 55, 441 NAS/NetWare 55 NAS/NetWare server entry 345 Navigation Tree administrative services 383 agent information 385 Data Manager node 416 Services 384 navigation tree 380 NDS trees 39 NDS trees discovery 39 NetBIOS 78 netstat command 52 NetWare 22, 355 NetWare servers considerations 39 network appliance 441 connectivity 62 filesystems 54
Q
quotas 343, 439
R
RDBMS 47, 373 RDBMS Logins 489 Redbooks Web site contact us xiii register a database 488
Index
577
registered agent availability 471 RegistrationPW parameter 126 related publications 571 removed resource retention 370 repocopy tool 559 Reporting capacity 472, 494, 497 filesystem capacity 475 groups 452 historical report 476 Reporting facility 450 reporting for databases 486 reports Access File Summary 399 Access Time Summary 394 agent availability 471 backup 482 batch output 412 By Computer 453 By Storage Subsystems 464 Computers 468 data paths 511 disk capacity 397 Disk Defects 399 Most at Risk Files 401 Most Obsolete Files 407 Oldest Orphaned Files 407 Probe History 457 standardized 7 Storage Access Time 399 Storage Availability 408 Storage Capacity 408 Storage Modification Times 401 subsystem 11 system 393 System-wide 466 Total Free Space 409 usage 477 usage reporting 477 Usage violations 482 User Quota Violations 408 User Space Usage 409 Virtual Machines 542 Wasted Space 410 reserved ports 72 residency program xiii Resource Manager 569 role-based administration 29 role-based security 58
role-based users 59 Rollup Report data tables 517 generation 524 Rollup Reporting subordinate servers 516 test TPC Server 520 Rollup Reporting categories 523
S
scan agent administration 344 Scan job 423 Scan job alerts 432433 scheduled actions 447 scheduler 385 Scheduler component log 386 Scheduler.config file 49 schema name 134, 197 script against monitored server 447 scripts 448 scripts for Data agent 317 Secure Sockets Layer (SSL) 24 security considerations 29 security certificates 60 Security Certificates window 116 server recommendations 48 server component log 386 server.config file 49 service accounts 61 service log 386 Service status 386 shutdown 388 silent install response file 300 SMIS 11 SMI-S Array Reporting 30 SMI-S support 17 SNIA CTP Certification 30 SNMP MIB 24 trap 24 software prerequisites 36 space-efficient volumes DS8000 16 standardized reports 7 storage subsystems 56 su command 169, 234
578
subordinate server 516 subsystem reporting 11 supported systems 29 system reports 393 system-managed space 45
T
tablespace 371 tablespace considerations 265 TagmaStore CIM agent 15 tape library support 56 tar command 240 TCP/IP ports 49 Tivoli Common Agent Services 27, 30 Tivoli Provisioning Manager 13 Tivoli Storage Manager 449 backup job 450 Tivoli Storage Manager Server backup and archive 404 Topology Viewer 11, 501 Context Sensitive 511 Data Path Explorer 511 hypervisor support 531 integrated reports 504 link to alerts 505 link to reports 507 pin list feature 502 pin list persistence 502 pinning 502 virtual computers 533 TotalStorage Productivity Center 565 Assistant 17 CIMOM configuration 356 component install 129 Data server 6 Device server 6 GUI login 280 Install using CD 257 license 131 overview 2 physical structure 4 structure 3 TotalStorage Productivity Center for Data architecture 8 clients 9 Data agent 9 Data manager 9 overview 7
Web server 9 TPC Data agent VMware considerations 41 TPC for Data architecture 17 TPC for Replication 5 TPC GUI launch 281 TPC Server housekeeping 553 TPC subordinate servers 521 TPC Superuser 142 TPCD.config file 17 TPCDB database 142 TPCDB default database name 45 Trace log files 387 TSM backup 404, 482 TSM required backup storage 484 TSRMsrv1 user ID 143 Typical installation 72, 92 user ID and password rules 79
U
universal agent 14 usage reporting 477 violations reporting 482 user group 421 user grouping 420 user ID 565, 568 user interface 21 User Rights Assignments 58
V
verify installation 126, 138 VMWare Mapping to Hypervisor 548 VMware Controllers details 539 data sources 41 ESX Server disks 540 Fabric agent 42 Filesystem Capacity 551 Filesystem report 550 Hypervisor Alerts 352, 434 LUN Correlation 541 LUN Definition 541 probe job 352 VI Data Source 12 Virtual Machines 542
Index
579
VirtualCenter 12 VMware ESX Server TPC configuration 347 VMware server keytool command 347 volume groups 458 volume managers 55
W
Web server 9 WebSphere Application Server 30 Connection Information 246 Windows domain 59 Windows Services 61 Windows space requirements 35
X
X Window System display 216
580
Back cover
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.