Certification Study Guide IBM Total Storage Productivity Center V3.1 - Sg247390

Front cover
Certification Study Guide: IBM TotalStorage Productivity Center for Data V3.1
Prepare for certification in theory and practice Gain practical experience with the provided examples and tips Contains a hands-on lab and sample test
Carlos Jos Otlora Yepes Bart Jacob
ibm.com/redbooks
International Technical Support Organization Certification Study Guide: IBM TotalStorage Productivity Center V3.1 January 2007
SG24-7390-00
Note: Before using this information and the product it supports, read the information in Notices on page ix.
First Edition (January 2007) This edition applies to Version 3, Release 1.2 of IBM Tivoli Productivity Center for Data.
Copyright International Business Machines Corporation 2007. 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 Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Chapter 1. Professional Certification Program overview . . . . . . . . . . . . . . 1 1.1 IBM Professional Certification Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.1 Benefits of certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.2 Tivoli Software Professional Certification . . . . . . . . . . . . . . . . . . . . . . 4 1.2 IBM Certified Deployment Professional: IBM TotalStorage Productivity Center for Data V3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2.1 Job role description / Target audience . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.2 Key areas of competency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.4 Test components and characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3 Test 900: Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3.1 Section 1: Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3.2 Section 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.3.3 Section 3: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.3.4 Section 4: Customization and administration . . . . . . . . . . . . . . . . . . 14 1.3.5 Section 5: Product demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.3.6 Section 6: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.4 Recommended resources for study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.4.1 Courses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.4.2 Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1.4.3 Other information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Chapter 2. Overview of IBM TotalStorage Productivity Center for Data. . 27 2.1 Introduction to IBM TotalStorage Productivity Center for Data . . . . . . . . . 28 2.2 Product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.1 Policy-based management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.2 Automatic file system extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.3 Tivoli Storage Manager integration . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.4 Subsystem reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.2.5 NAS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.2.6 Advanced provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Copyright IBM Corp. 2007. All rights reserved.
iii
2.2.7 Comprehensive reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.2.8 Monitoring and alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.2.9 Database support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.2.10 Chargeback support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.3 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.3.1 Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.3.2 Schema of interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.3 Data Manager - server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.3.4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3.5 Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 2.3.6 Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 2.3.7 Integration points with TEC and IBM Tivoli Storage Manager . . . . . 40 2.3.8 Tivoli Common Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 2.3.9 Role-based Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 2.4 Supported environments for Version 3 Release 1. . . . . . . . . . . . . . . . . . . 45 Chapter 3. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.1 What you should know about the planning section of the test objectives . 48 3.2 Summary of changes for IBM TotalStorage Productivity Center for Data Version 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 3.2.1 Technical changes for Version 3 Release 1 . . . . . . . . . . . . . . . . . . . 48 3.2.2 Functions no longer provided in TPC V3.1 . . . . . . . . . . . . . . . . . . . . 50 3.3 IBM TotalStorage Productivity Center for Data V3.1 system requirements and supported systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 3.3.1 Hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 3.3.2 Disk space requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3.3.3 Software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.3.4 Novell NetWare considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 3.3.5 NAS environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.3.6 Databases supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.3.7 Data Manager database repository . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.3.8 Agent Manager database repository . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.3.9 SMS or DMS tablespace type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.3.10 Database Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 3.3.11 Data agent monitored databases . . . . . . . . . . . . . . . . . . . . . . . . . . 60 3.4 Pre-installation steps for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.4.1 Installable components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.4.2 Order of component installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.4.3 Server recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.4.4 Installation port requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.4.5 Supported file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 3.4.6 Supported network file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 3.4.7 Support for NAS/NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
iv
Certification Study Guide: IBM TotalStorage Productivity Center V3.1
3.4.8 Disk and volume group support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3.4.9 Storage subsystem support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3.4.10 Tape library support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 3.4.11 User IDs and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 3.4.12 Certificates and key files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3.4.13 Services and service accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3.4.14 Starting and stopping the managers . . . . . . . . . . . . . . . . . . . . . . . . 73 3.5 Analyzing and defining environment requirements . . . . . . . . . . . . . . . . . . 74 3.5.1 Agent installation methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.5.2 Local installation of the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 3.5.3 Remote installation of the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 3.5.4 Interoperability namespace summary table . . . . . . . . . . . . . . . . . . . 77 3.6 Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Chapter 4. Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 4.1 What you should know about the installation section of exam objectives . 82 4.2 Installing TotalStorage Productivity Center . . . . . . . . . . . . . . . . . . . . . . . . 82 4.2.1 Installing Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 4.2.2 Installing Agent Manager on Windows . . . . . . . . . . . . . . . . . . . . . . . 84 4.2.3 Typical installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 4.2.4 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 4.2.5 CD layout and components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 4.2.6 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 4.3 Windows installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4.3.1 DB2 install for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4.3.2 Agent Manager install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 4.3.3 Install TotalStorage Productivity Center components . . . . . . . . . . . 127 4.3.4 Installing Data server, Device server, GUI, and CLI . . . . . . . . . . . . 135 4.4 GUI for Web Access under Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . 144 4.4.1 Installing Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . 145 4.4.2 Configuring IIS for the TotalStorage Productivity Center GUI . . . . . 148 4.4.3 Launch the TotalStorage Productivity Center GUI . . . . . . . . . . . . . 152 Chapter 5. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 5.1 Agent deployment options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 5.2 Local installation of Data and Fabric Agents . . . . . . . . . . . . . . . . . . . . . . 159 5.2.1 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 5.3 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 5.3.1 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 5.4 Upgrading the Data Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 5.5 Alert disposition (SNMP and mail). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.6 Log file retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 5.6.1 Quota and constraint e-mail address rules . . . . . . . . . . . . . . . . . . . 182
Contents
5.7 Scan/probe agent administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 5.7.1 Manual NAS/NetWare server entry . . . . . . . . . . . . . . . . . . . . . . . . . 184 5.8 History aggregator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 5.8.1 Data Manager NetWare tree logins. . . . . . . . . . . . . . . . . . . . . . . . . 187 5.9 Data Manager CIMOM logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 5.9.1 Configuring CIMOMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 5.10 Data Manager resource history retention . . . . . . . . . . . . . . . . . . . . . . . 200 5.10.1 Removed resource retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 5.10.2 Resource history retention for databases . . . . . . . . . . . . . . . . . . . 202 5.10.3 Removed resource retention for databases . . . . . . . . . . . . . . . . . 202 5.10.4 Adding databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 5.11 Configuring chargeback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Chapter 6. Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 6.1 Using Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 6.1.1 Starting the user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 6.1.2 Administrative services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6.2 Report function of the Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 6.2.1 Predefined reports under the My Reports node . . . . . . . . . . . . . . . 222 6.2.2 Batch reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 6.2.3 Creating Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 6.2.4 Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 6.3 Data Manager Navigation Tree path . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 6.3.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 6.3.2 Pings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 6.3.3 Creating Scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 6.3.4 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 6.3.5 Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 6.3.6 Policy management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 6.4 Reporting facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 6.4.1 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 6.4.2 Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 6.4.3 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 6.4.4 Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 6.4.5 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 6.4.6 Usage violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 6.4.7 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Chapter 7. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 7.1 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 7.2 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.3 Audit logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.4 Diagnosing IBM TotalStorage Productivity Center problems . . . . . . . . . 305
vi
7.4.1 General information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 7.5 Troubleshooting CIM Agents and discovery . . . . . . . . . . . . . . . . . . . . . . 306 7.6 Troubleshooting tpctool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 7.6.1 Common user errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 7.6.2 srmcp commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 7.7 Troubleshooting discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 7.7.1 Common user errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 7.8 Troubleshooting IBM TotalStorage Productivity Center for Data . . . . . . 312 7.8.1 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 7.9 Problem descriptions and solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 7.9.1 Installation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 7.9.2 Reporting and GUI problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 7.9.3 Switch problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 7.9.4 Miscellaneous problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Appendix A. Hands-on lab example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Getting started with TPC for Data lab exercise . . . . . . . . . . . . . . . . . . . . . . . 326 Exercise 1: Getting started with TPC for data . . . . . . . . . . . . . . . . . . . . . . 327 Exercise 2: Run a Scan job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Exercise 3: Define a quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Exercise 4: Define a Constraint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Appendix B. Sample questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Sample test 900: Questions and answers . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Answer key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
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
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX 5L AIX Cloudscape DB2 Universal Database DB2 DS4000 DS6000 DS8000 Enterprise Storage Server IBM ibm.com NetView Power PC POWER4 POWER5 Redbooks Redbooks (logo) System i System p System x System z System Storage Tivoli Enterprise Tivoli Enterprise Console Tivoli TotalStorage WebSphere
The following terms are trademarks of other companies: Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Network Appliance, WAFL, Data ONTAP, NetApp, and the Network Appliance logo are trademarks or registered trademarks of Network Appliance, Inc. in the U.S. and other countries. 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. Internet Explorer, Microsoft, Windows NT, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Pentium, Xeon, 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
This IBM Redbook is a study guide for IBM TotalStorage Productivity Center for Data Version 3.1, and it is targeted for professionals who want to get an IBM Certification in this specific product. This Certification, offered through the Professional Certification Program from IBM, is designed to validate the skills required of technical professionals who work in the implementation of the IBM TotalStorage Productivity Center for Data Version 3.1 product. This IBM Redbook provides a combination of theory and practical experiences necessary for a general understanding of the subject matter. It also provides sample questions that will help in the evaluation of personal progress and provide familiarity with the types of questions that will be encountered in the exam. This IBM Redbook does not replace practical experience, nor is it designed to be a stand-alone guide for any subject. Instead, it is an effective tool that, when combined with education activities and experience, can be a useful preparation guide for the exam.
The team that wrote this IBM Redbook

This IBM Redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, Austin, TX Center. Carlos Jos Otlora Yepes is currently working as a Tivoli Technical Specialist in the IBM Business Partner Innovation Center (BPIC) in Colombia with NEXSYS DE COLOMBIA S.A. (The IBM Software VAD in Colombia). He holds a Bachelor of System Administration degree in Computer Science and a degree in Security Management. He has 19 years of experience in the IT field. He has Technical certifications in IBM Certified Deployment Professional - Tivoli Productivity Center For Data, IBM Certified Deployment Professional - Tivoli Storage Manager, and Microsoft Certified Professional - MCP
xi
Bart Jacob is a Senior Consulting IT Specialist at IBM Corp - International Technical Support Organization, Austin Center. He has over 25 years of experience providing technical support across a variety of IBM products and technologies, including communications, object-oriented software development, and systems management. He has over 14 years of experience at the ITSO, where he has been writing IBM Redbooks and creating and teaching workshops around the world on a variety of topics. He holds a Masters degree in Numerical Analysis from Syracuse University.
Figure 1 Carlos Jos Otlora Yepes and Bart Jacob
Thanks to the following people for their contributions to this project: Authors of the Deployment Guide Series: TotalStorage Productivity Center for Data, SG24-7140 (from which a large amount of content has been borrowed): Mary Lovalace International Technical Support Organization, San Jose Center Harmut Harder IBM Germany
xii
Elizabeth Purzer WW Tivoli Channels Program Manager
Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll have the opportunity to team with IBM technical professionals, Business Partners, and Clients. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us! We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an e-mail to: redbooks@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
Preface
xiii
xiv
Chapter 1.
Professional Certification Program overview

This chapter provides an overview of the skill requirements necessary to obtain an IBM Advanced Technical Expert certification. The specific topics are designed to provide a comprehensive review for obtaining the certification: IBM Professional Certification Program IBM TotalStorage Productivity Center for Data V3.1 Implementation Certification Recommended study resources
1.1 IBM Professional Certification Program

Having the right skills for the job is critical in the growing global marketplace. IBM Professional Certification, designed to validate skill and proficiency in the latest IBM solution and product technology, can help provide that competitive edge. The IBM Professional Certification Program Web site is available at: http://www.ibm.com/certify/ The Professional Certification Program from IBM offers a business solution for skilled technical professionals seeking to demonstrate their expertise to the world. The program is designed to validate your skills and demonstrate your proficiency in the latest IBM technology and solutions. In addition, professional certification may help you excel at your job by giving you and your employer confidence that your skills have been tested. You may be able to deliver higher levels of service and technical expertise than non-certified employees and move on a faster career track. Professional certification puts your career in your control. This is a way for skilled IT professionals to demonstrate their expertise to the world. It validates your skills and demonstrates your proficiency in the latest IBM technology and solutions. The certification requirements are tough, but not impossible. Certification is a rigorous process that differentiates you from everyone else. The mission of IBM Professional Certification is to: 1. Provide a reliable, valid, and fair method of assessing skills and knowledge. 2. Provide IBM with a method of building and validating the skills of individuals and organizations. 3. Develop a worldwide community of highly skilled certified professionals who recommend, sell, service, support, teach, or use IBM products and solutions. The Professional Certification Program from IBM has developed certification role names to guide you in your professional development. The certification role names include IBM Certified Specialist, IBM Certified Solutions/Systems Expert, and IBM Certified Advanced Technical Expert for technical professionals who sell, service, and support IBM solutions. For technical professionals in application development, the certification roles include IBM Certified Developer Associate and IBM Certified Developer. IBM Certified Instructor certifies the professional instructor.
The Professional Certification Program from IBM provides you with a structured program leading to an internationally recognized qualification. The program is designed for flexibility by allowing you to select your role, prepare for and take tests at your own pace, and, in some cases, select from a choice of elective tests best suited to your abilities and needs. Some roles also offer a shortcut by giving credit for a certification obtained in other industry certification programs. You may be a network administrator, systems integrator, network integrator, solution architect, solution developer, value-added reseller, technical coordinator, sales representative, or educational trainer. Regardless of your role, you can start charting your course through the Professional Certification Program from IBM today.
1.1.1 Benefits of certification

Certification is a tool to help objectively measure the performance of a professional on a given job at a defined skill level. Therefore, it is beneficial for individuals who want to validate their own skills and performance levels, their employees, or both. For optimum benefit, the certification tests must reflect the critical tasks required for a job, the skill levels of each task, and the frequency by which a task needs to be performed. IBM prides itself on designing comprehensive, documented processes that ensure that IBM certification tests remain relevant to the work environment of potential certification candidates. In addition to assessing job skills and performance levels, professional certification may also provide such benefits as: For employees: Promotes recognition as an IBM certified professional Helps to create advantages in interviews Assists in salary increases, corporate advancement, or both Increases self esteem Provides continuing professional benefits To obtain new opportunities of professional development For employers: Measures the effectiveness of training Reduces course redundancy and unnecessary expenses Provides objective benchmarks for validating skills Makes long-range planning easier Helps to manage professional development
Chapter 1. Professional Certification Program overview
Aids as a hiring tool Contributes to competitive advantage Increases productivity, morale, and loyalty For Business Partners and consultants: Provides independent validation of technical skills Creates competitive advantage and business opportunities Enhances prestige of the team Contributes to IBM requirements for various IBM Business Partner programs To increase the sales of the products. Specific benefits may vary by country (region) and role. In general, after you become certified, you should receive the following benefits: Industry recognition Certification may accelerate your career potential by validating your professional competency and increasing your ability to provide solid, capable technical support. Program credentials As a certified professional, you receive an e-mail with your certificate of completion and the certification mark associated with your role for use in advertisements and business literature. You may also request a hardcopy certificate, which includes a wallet-size certificate. The Professional Certification Program from IBM acknowledges the individual as a technical professional. The certification mark is for the exclusive use of the certified individual. Ongoing technical vitality IBM Certified professionals are included in mailings from the Professional Certification Program from IBM.
1.1.2 Tivoli Software Professional Certification

Tivoli's professional certification program offers certification testing that sets the standard for qualified product consultants, administrators, architects, and partners. The program also offers an internationally recognized qualification for technical professionals who are seeking to apply their expertise in today's complex business environment. The program is designed for those who implement, buy,
sell, service, and support Tivoli solutions and want to deliver higher levels of service and technical expertise to IBM customers. Whether you are a Tivoli customer, partner, or technical professional wishing to put your career on the fast track, you can start your journey to becoming a Tivoli Certified Professional today.
Other benefits of Tivoli Certification

Tivoli Certification has the following benefits: For the individual: IBM Certified certificate and use of Tivoli logos on business cards. Note: Certificates are sent by e-mail; however, a paper copy of the certificate and a laminated wallet card can also be requested by sending an e-mail to certify@us.ibm.com. Recognition of your technical skills by your peers and management Possibility of giving back to the technical community by being a resource for other less experienced technicians Enhanced career opportunities Focus for your professional development For the Business Partner Confidence in the skills of your employees Enhanced partnership benefits from Business Partner Program Higher rates for billing out your employees Stronger customer proposals Demonstration of the depth of technical skills available to prospective customers For the client: Confidence in the services of professionals handling your implementation Ease of hiring competent employees to manage your Tivoli environment Enhanced return on investment (ROI) through more thorough integration with Tivoli and third-party products Ease of selecting a Tivoli Business Partner that meets your specific needs in the Tivoli Products for your implementation solution
Certification checklist
In preparing for certification, this checklist may be helpful: 1. Select the certification you want to pursue. 2. Determine which tests are required by reading the certification role description. 3. Determine the study resources required to prepare for Tivoli Certification. 4. Prepare for the test using the following resources: Test objectives for the Tivoli Certification Recommended educational resources (for example, this IBM Redbook or Virtual Integration Center (VIC) Courses) Sample/assessment test Other reference materials Opportunities for experience Note: These resources are available from each certification description Web page, as well as from the Test information Web page. 5. Register to take a test by contacting one of our worldwide testing vendors: Thomson Prometric Pearson VUE (Virtual University Enterprises) Note: When providing your name and address to the testing vendor, be sure to specify your name exactly as you want it to appear on your certificate 6. Take the test. Be sure to keep the Examination Score Report provided upon test completion, as your record of taking the test. Note: After you take the test, the results and demographic data (such as name, address, e-mail, and phone number) are sent from the testing vendor to IBM for processing (please allow two to three days for transmittal and processing). Once all the tests required for a certification are passed and received by IBM, your certificate will be issued. 7. Repeat Steps 3 through 5 until all required tests are successfully completed for the certification. If there are additional requirements (such as another vendor certification or exam), please follow the instructions on the certification description page to submit these requirements to IBM.
8. Once you meet the requirements, you will be sent an e-mail asking you to accept the terms of the IBM Certification Agreement. 9. Upon your acceptance, you receive an e-mail with the following deliverable: A Certification Certificate in .pdf format, which can be printed in either color or black and white. A set of graphic files containing the IBM Professional Certification mark associated with the certification achieved. Guidelines for the use of the IBM Professional Certification mark. 10.To avoid unnecessary delay in receiving your certificate, please ensure that your current e-mail is on file by keeping your profile up to date. If you do not have an e-mail address on file, your certificate will be sent by postal mail. Once you receive a certificate by e-mail, you may also contact IBM at certify@us.ibm.com to request that a hardcopy certificate be sent by postal mail. Note: IBM reserves the right to change or delete any portion of the program, including the terms and conditions of the IBM Certification Agreement, at any time without notice. Some certification roles offered through the IBM Professional Certification Program require recertification.
1.2 IBM Certified Deployment Professional: IBM TotalStorage Productivity Center for Data V3.1
You will get the following discount when you take the exam: Important: IBM offers a promotion code below, which is good for a 15 percent discount on the indicated Tivoli certification exams if taken at any Thomson Prometric or Pearson VUE testing centers. Code: 15T900. Percent off: 15 percent. Valid for exams: 000-900. Expires: Code is valid as long as exam is available.
1.2.1 Job role description / Target audience

An IBM Certified Deployment Professional - TotalStorage Productivity Center for Data V3.1 is a person who performs the requirements gathering and planning for the IBM TotalStorage Productivity Center deployment and integration into a computing environment. This person performs installation, configuration, administration, and problem determination of the IBM TotalStorage Productivity Center for Data V3.1 software. It is expected that this person will be able to perform these tasks with limited assistance from peers, product documentation, and vendor support services.
1.2.2 Key areas of competency

This person is expected to perform the following tasks independently: Assess customer requirements and create a solution design. Analyze the deployment environment. Develop and implement the project plan. Apply storage management concepts. Perform basic installation of the prerequisite applications (supported RDBMS). Describe the IBM TotalStorage Productivity Center for Data V3.1 features and components. Demonstrate general understanding of storage subsystems. Troubleshoot IBM TotalStorage Productivity Center for Data V3.1 components.
1.2.3 Prerequisites
To attain the IBM Certified Deployment Professional - IBM TotalStorage Productivity Center for Data certification, candidates must pass one test. The following prerequisites are necessary: Working knowledge of supported operating systems Basic understanding of basic networking, TCP/IP, and SNMP Basic skills for DB2 and supported RDMS databases System administration skills, including working knowledge of account management Working knowledge of storage hardware technologies (NAS, DAS, and SAN) Working knowledge of distributed server technologies
General storage concepts Working knowledge of IBM TotalStorage Productivity Center for Data V3.1 Working knowledge of storage replication Basic skills for WebSphere Application Server Express V5.0
1.2.4 Test components and characteristics

This test has the following components and characteristics: IBM Certified Deployment Professional - TotalStorage Productivity Center for Data V3.1 Test 900: IBM TotalStorage Productivity Center for Data V3.1 Implementation Test 900 Objectives Test 900 Sample test Test 900 Recommended educational resources Approximate number of questions: 57 Duration in minutes: 90 Format: Multiple choice Required passing score: 70% or 33 correct answers
1.3 Test 900: Objectives

Test 900 has five areas or sections of objectives, as described below.
1.3.1 Section 1: Planning

Given the customers business objectives and storage environment, gather and analyze the customers storage management requirements so that a solution that meets customer expectations can be implemented, with emphasis on performing the followings steps: Identify automated action requirements. Identify integration points with other products. Recommend a database. Define a user base. Analyze environment. Reporting requirements. Agent distribution methodology. Verify ports (TSRM/TCP) are available.
TotalStorage Productivity Center for Data server sizing. Resume gathering and analyzing customers storage management requirements. Given the customers TPC hosting requirements, verify that software and hardware resources for the TPC Server and Agent Manager server are available so that TPC Server and Agent Manager can be successfully installed. with emphasis on performing the following steps: Verify supported OS is available for the TPC Server. Verify TPC Server resources are sufficient. Verify supported OS is available for the Agent Manager server. Verify Agent Manager server resources are sufficient. Given the customers storage hardware (switches, disk, tape, SAN and other devices), verify that firmware levels of storage hardware are supported, so that compliance with TPC software is achieved, with emphasis on performing the following steps: Identify Disk sub-systems. Identify SAN Switches. Identify Tape Libraries. Validate Hardware Firmware levels. Given the customers storage management requirements, identify agent candidates and types and verify that they meet supported hardware/software prerequisites, so that TPC agents can be successfully installed, with emphasis on performing the following steps: Identify agent candidates. Verify agents meet hardware and software prerequisites. Determine agent distribution methodology. Given the customer requirements for managing file systems, databases, and SAN devices, identify required DBA and OS user IDs and required CIM/OMs so that their environment can be properly discovered, probed, and scanned, with emphasis on performing the following steps: Identify and verify required DBA and OS user IDs. Identify and verify required CIM/OMs. Common Agent user ID. Given a supported TPC environment, network and storage management requirements, architect a TPC Server and Database repository, so that a
10
successful TPC installation can be achieved, with emphasis on performing the following steps: Determine Network Configuration. Verify ports are available. Identify Database size and location. Size the TPC Server. Given managements commitment, document the environment, resources, components and user base so that an architectural document can be created, with emphasis on performing the following steps: Document the environment, resources, components, and user base. Gather automated action requirements. Identify integration points with other products. Define user base. Define reporting requirements. Given the architectural document, create a task list that maps solutions to products so that a Project Plan can be developed, with emphasis on performing the following steps: Create a task list. Map customer requirements to product functions. Assemble resources to be used in projects.
1.3.2 Section 2: Installation

Given that DB2 is installed, determine if systems resources, access, and a new DB2 instance exist so that TPC can be installed, with emphasis on performing the following steps: Verify if system resources and access are available. Create a DB2 instance. Verify privileges. Verify and enable an RDBMS listening port. Verify that a UID password exists on the database server.
11
Given the TPC media, perform installation steps using an installer method so that TPC Agent Manager is successfully installed and running, with emphasis on performing the following steps: Check for the latest technical resource flashes on the TPC support Web site. Perform the installation steps using the appropriate OS installer method, for example, Smitty for AIX, silent command for Linux, or the wizard for Windows. Verify DB2 is up and running. Given TPC media, perform installation steps using an installer method so that TPC Server is successfully installed and running, with emphasis on performing the following steps: Check for the latest technical resource flashes on the TPC support Web site. Perform the installation steps using the appropriate OS installer method, for example, Smitty for AIX, silent command for Linux, or a wizard for Windows. Verify DB2 and Agent Manager are up and running. Log in to the TPC GUI to verify installation. Given a successful install, determine if errors exist in the install logs, so that the installation is verified, with emphasis on performing the following steps: Start the TPC GUI. Run a Discovery job. Go to appropriate log directory in Windows or UNIX Review log file for server and agent. If errors are found, take the appropriate troubleshooting steps. In TPC GUI, go to administrative services and verify that all services are up. In TPC GUI, go to administrative services/agents and verify that the agent is active.
1.3.3 Section 3: Configuration

Given a successfully installed TPC server, configure licenses so that TPC can function in compliance with the license agreement, with emphasis on performing the following steps: Enter license keys. License computers.
12
Given the customer Operating System user account groups, map the TPC roles to OS user account groups so that role based management can be created, with emphasis on performing the following steps: Create user account groups for mapping if not already created. Map roles to user account groups. Given the CIM/OM server IP address or host name, verify the CIM/OM is operational so that it can be defined to the TPC Server, with emphasis on performing the following steps: Verify CIM/OM operation. Given an operational CIM/OM, define it to the TPC server so that storage devices can be discovered and managed as needed, with emphasis on performing the following steps: Identify CIM/OM login. Configure CIM/OM to TPC server. Given the IP Address or host name of the NAS device, define and assign a Scan/Probe Agent so that TPC can access the NAS device, with emphasis on performing the following steps: Manually enter the server information and SNMP community name. Assign a Scan/Probe Agent. Given a successfully discovered Novell Directory Services (NDS) tree, define the NetWare servers to TPC so that TPC can access the NDS tree, with emphasis on performing the following step: Manually enter the host name or IP address of the NetWare Server and the login information. Given a customer requirement for alert routing, configure the alerts to go to the appropriate SNMP manager or TEC, so that TPC meets their requirements, with emphasis on performing the following steps: Configure SNMP parameters. Configure TEC. Given a licensed computer with a supported RDBMS installed, successfully configure and collect statistics on the given Database so that RDBMS data can be collected, with emphasis on performing the following steps: Choose a host name and database type. Enter relevant database information. Create and run a database probe job. Create and run a database scan job.
13
Given a successfully installed TPC server, Data agent, Fabric agent, CIM agent, and properly configured SNMP community names, run a discovery so that storage devices can be discovered, with emphasis on performing the following steps: Run CIM/OM discovery. Run Out of Band Fabric discovery. Run NetWare Filer discovery. Run Windows Domain, NAS, and SAN FS discovery. Given a successfully discovered storage environment, define monitoring jobs for data collection so that TPC can report on storage resources, with emphasis on performing the following steps: Create and run appropriate ping jobs. Create and run appropriate probe jobs. Create and run appropriate scan jobs. Given a successfully configured TPC environment, create documentation so that the customer will have a record of their configuration, with emphasis on performing the following steps: Record configuration information.
1.3.4 Section 4: Customization and administration

Given a working TPC environment and customer requirements, create profiles so that specific reports can be generated, with emphasis on performing the following step: Create profiles. Given a working TPC environment and customer requirements, set history retention so that it meets customer requirements, with emphasis on performing the following step: Set history retention periods. Given a working TPC environment and group membership requirements, create monitoring groups so that jobs can be run, with emphasis on performing the following steps: Create computer groups. Create file system groups. Create directory groups. Create user groups.
14
Create OS user groups. Assign resources to groups. Given a working TPC environment and customer requirements, create custom policies so that they meet customers business requirements, with emphasis on performing the following steps: Set quotas. Schedule data collection activities. Configure alert constraints. Given a working TPC environment and customer requirements, perform backups so that customer backup requirements are met, with emphasis on performing the following step: Back up Agent Manager and TPC repositories, configuration files, and certification files.
1.3.5 Section 5: Product demonstration

Given customer requirements to monitor NAS and NetWare, perform discovery or manual assignments so that TPC can be configured to monitor these devices, with emphasis on performing the following steps: Knowledge transfer. Product demonstration Perform discovery or manual assignments of NAS and NetWare. For other NAS, verify that SNMP enterprise OID vendor number exists in NAS and the configure file. Run a discovery job to discover the NDS/edirectory trees and NAS. Configure NDS login for the desired NDS tree. Assign agents to scan/probe each file system "scan probe agent admin". Run a Discovery job. Verify customer understanding of concepts. Given a functioning TPC environment and configured SAN fabric switches, create a zone and zone set, so that TPC zone management functionality can be demonstrated, with emphasis on performing the following steps: Create zone set. Create zone. Activate zone set.
15
Given a successful discovery, configure and run a Probe so that an inventory can be collected, with emphasis on performing the following steps: Knowledge transfer to customer. Product demonstration. Select the agents (computers) to be probed, when to Probe, Triggered Condition/Alert Action. Define Groups. Define Profiles. Run a Probe. Generate an Asset Report. Verify customer understanding of concepts. Given successful agent deployment, run a Ping so that Availability Reports can be generated, with emphasis on performing the following steps: Knowledge transfer to customer. Product demonstration. Select agents (computers) to be pinged. Choose when to Ping. Choose how often to save the Ping statistics (Options tab). Choose Triggered Condition/Action. Run the ping. Verify customer understanding of concepts. Given a successful Probe, run a Scan against the inventory, so that the administrator can gather file system level information, with emphasis on performing the following steps: Knowledge transfer. Product demonstration. Select computers or file systems to be scanned. Select the Profile(s). Choose when to Scan. Choose Triggered Condition/Action. Run a Scan. Verify customer understanding of concepts.
16
Given a successful Probe, run a Scan against the inventory, so that the administrator can gather selected information about the environment, with emphasis on performing the following steps: Knowledge transfer. Product demonstration. Select computers or file systems to be scanned. Select the Profile(s). Choose when to Scan. Choose Triggered Condition/Action. Run a Scan. Verify customer understanding of concepts. Given customer requirements for alerting, configure an Alert so that TPC can send alerts where needed, with emphasis on performing the following steps: Knowledge transfer. Product demonstration. Select computers or file systems to be scanned Define trigger condition. Define trigger action (TEC, SNMP, Login Notification, Event Logs, Email, or Scripts). Configure parameters for selected trigger action (for example, load Tivoli). Enterprise Console TEC_ baroc file for event file; configure SNMP parameters, SNMP communicator, and compile MIB). Run a Scan. Verify customer understanding of concepts. Given a customer requirement to monitor RDBMS, configure TPC for Database on the server so that database reporting can be performed, with emphasis on performing the following steps: Knowledge transfer to customer. Product demonstration. Select the appropriate agent and enable TPC for databases for that agent. Define RDBMS login for the appropriate database and agent. Define database groups. Define alerting. Define and run a Probe.
17
Define profiles. Define a quota. Run a Scan. Generate reports. Verify customer understanding of concepts. Given a successful TPC Server installation, set up a Batch report for violating constraints for file types and enable HTML output for Web site reporting, with emphasis on performing the following steps: Knowledge transfer to customer. Product demonstration. Create a Constraint for file types. Create a Profile. Define and run a Probe. Run Scan with file types Profile. Create Batch report (Select Computers, When to run, or Triggered Condition/Alert). Create html batch reports for Web sites. Web server identified. Verify customer understanding of concepts. Given an installed CIM/OM, configure the CIM/OM so that TPC can perform discovery, monitoring, and reporting, with emphasis on performing the following steps: Knowledge transfer to customer. Product demonstration. Define CIM/OM login on a TPC server using a CIM/OM login host name. Perform a discovery and review output logs. Enable TPC "monitoring" for storage subsystem administration. Create and run a TPC Probe for storage subsystem. Verify customer understanding of concepts.
18
Given a functioning TPC environment and a configured storage subsystem, create a performance monitor and alert so that subsystem performance monitoring and alerting functionality can be demonstrated, with emphasis on performing the following steps: Create performance monitor. Create performance alert and set thresholds. Given a functioning TPC environment and a configured storage subsystem, create a performance report so that storage subsystem performance reporting functionality can be demonstrated, with emphasis on performing the following steps: Create performance report.
1.3.6 Section 6: Troubleshooting

Given a malfunctioning TPC environment, identify the directory and appropriate log files so that the log file can be used for troubleshooting, with emphasis on performing the following steps: Locate log file directories and log files. Given malfunctioning TPC environment and a serviceability tool output request from IBM support, generate the serviceability report files so that they can be used for troubleshooting, with emphasis on performing the following steps: Run serviceability tool. Review operating system logs. Review run log data. Capture error message. Check TotalStorage Productivity Center for Data support Web site. Open PMR. Given a previously working TotalStorage Productivity Center for Data installation, review logs and known environment changes and determine whether the error is isolated to a system, intermittent, or platform dependent to resolve GUI connectivity, with emphasis on performing the following steps: Isolate the impact of the error to single or multiple instances. Identify the type of failure: solid or intermittent. Check local, remote, and Web GUI. Identify what platforms are affected. Review environmental changes.
19
Review operating system logs. Check the TotalStorage Productivity Center for Data support Web site. Open PMR.
1.4 Recommended resources for study

Courses and publications are offered to help you prepare for the certification tests. The courses are recommended, but not required, before taking a certification test. If you want to purchase Web-based training courses or are unable to locate a Web-based course or classroom course at the time and location you desire, please feel free to contact one of our delivery management teams at: Americas: tivamedu@us.ibm.com EMEA: tived@uk.ibm.com Asia-Pacific: tivtrainingap@au1.ibm.com. Note: Course offerings are continuously being added and updated. If you do not see the courses below listed in your geographical location, please contact the delivery management team.
1.4.1 Courses
The following section describes key courses related to IBM Tivoli Productivity Center for Data that are available.
Differences for IBM TotalStorage Productivity Center V3.1

Course duration: Eight (8) hours, Computer-Based Training (CBT) Course number: (Course numbers vary depending on the education delivery arm used in each geography. Please refer to the Web site below to find the appropriate course number according to the education delivery vendor chosen. Geo education page: Worldwide schedules are available at Tivoli software education at: http://www.ibm.com/software/tivoli/education/
20
Abstract: This course will cover the differences between IBM TotalStorage Productivity Center (TPC) Version 3.1 and TPC Version 2.3. Through recorded demonstrations and presentations, you will learn how installation, configuration, and operation of TPC has improved in the latest release. Topics include the new consolidated graphical user interface, new hardware support, new features, and the requirements for a successful migration from TPC V2.3.
IBM TPC V3.1 Installation and Basic Configuration

Course duration: Four (4) hours, Computer-Based Training (CBT) Course number: Course numbers vary depending on the education delivery arm used in each geography. Please refer to the Web site below to find the appropriate course number according to the education delivery vendor chosen. Geo education page: Worldwide schedules are available at Tivoli software education. Abstract: IBM TotalStorage Productivity Center (TPC) provides a set of policy-driven automated tools for managing storage capacity, availability, events, performance, and assets in an enterprise environment. IBM TotalStorage Productivity Center can help identify, evaluate, control, and predict 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 you define. In this course, the student will be guided through planning a deployment of IBM TotalStorage Productivity Center. Guided Practice exercises will simulate the installation of TPC and the prerequisite products in a Windows 2003 environment. This is Part 1 of 5 in the TPC V3.1 Web training series: IBM TotalStorage Productivity Center V3.1 Installation and Basic Configuration IBM TotalStorage Productivity Center V3.1 Data Management: Functions, Monitoring, and Alerts IBM TotalStorage Productivity Center V3.1 Data Management: Policy Management, Reporting, Database, and Chargeback IBM TotalStorage Productivity Center V3.1 Fabric Management IBM TotalStorage Productivity Center V3.1 Disk Management Note: A CBT is available at no charge to Business Partners within the Virtual Innovation Center at: http://www.ibm.com/jct09002c/isv/welcome/vic.html
21
For information about pricing, scheduling and course registration: Course names and course numbers vary depending on the education delivery arm used in each geography. Please refer to the Tivoli software education Web site to find the appropriate course and education delivery vendor for each geography. This section provides information about pricing, scheduling, and course registration. Course names and numbers vary depending on the education delivery arm used in each region. Please refer to the Tivoli software education Web site to find the appropriate course and education delivery vendor for each geography. General training information can also be found at this Web site: http://ibm.com/training
IBM TotalStorage Productivity Center V3.1

Course duration: Five (5) days, Instructor Led Training (ILT). Course number: (Course numbers vary depending on the education delivery arm used in each geography. Please refer to the Web site below to find the appropriate course number according to the education delivery vendor chosen. Geo education page: Worldwide schedules available at Tivoli software education at: http://www.ibm.com/software/tivoli/education/ Abstract: IBM TotalStorage Productivity Center (TPC) provides a set of policy-driven automated tools for managing storage capacity, availability, events, performance, and assets in an enterprise environment. IBM TotalStorage Productivity Center can help identify, evaluate, control, and predict 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 you define. In this course, the student will learn to install, configure, and administer IBM TotalStorage Productivity Center V3.1 in a Windows 2003 environment. Additional demonstrations will include lessons on TPC V3.1 for Red Hat Linux Advanced Server 3.0 and AIX 5L V5.3. The course will provide hands-on lab exercises to reinforce instructor based lectures and demonstrations. Note: A CBT is available at no charge to Business Partners within the Virtual Innovation Center.
22
For information about pricing, scheduling and course registration: Course names and course numbers vary depending on the education delivery arm used in each geography. Please refer to the Tivoli software education Web site to find the appropriate course and education delivery vendor for each geography. General training information can also be found at: http://www.ibm.com/training
1.4.2 Publications
The following publications may prove useful. IBM TotalStorage Productivity Center V3.1: The Next Generation, SG24-7194 Abstract: IBM TotalStorage Productivity Center is a suite of infrastructure management software that can centralize, automate, and simplify the management of complex and heterogeneous storage environments. It can help reduce the effort of managing complex storage infrastructures, improve storage capacity utilization, and improve administration efficiency. IBM TotalStorage Productivity Center allows you to respond to on demand storage needs and brings together, in a single point, the management of storage devices, fabric, and data. TotalStorage Productivity Center V3.1 is a rewrite of previous versions. This IBM Redbook will show you how to access the functions as compared to the previous releases. This IBM Redbook is intended for administrators and users who are installing and using IBM TotalStorage Productivity Center. It provides an overview of the product components and functions. It describes the hardware and software environment required and provides a step- by-step installation procedure. Customization and usage hints and tips are also provided. Exploring Storage Management Efficiencies and Provisioning Understanding IBM TotalStorage Productivity Center and IBM TotalStorage Productivity Center with Advanced Provisioning, SG24-6373 Abstract: This IBM Redbook provides an overview of the solution offerings IBM TotalStorage Productivity Center and IBM TotalStorage Productivity Center with Advanced Provisioning. It presents an overview of the product components and functions, explaining the architecture and showing the use of storage provisioning workflows. This IBM Redbook is intended for those who want to learn more about IBM TotalStorage Productivity Center, IBM TotalStorage Productivity Center with Advanced Provisioning, and IBM TotalStorage Provisioning Manager.
23
Product documentation
IBM TotalStorage Productivity Center for Data product documentation: IBM TotalStorage Productivity Center for Data Installation and Configuration Guide, GC32-1727 IBM TotalStorage Productivity Center for Data User's Guide, GC32-1728 IBM TotalStorage Productivity Center for Data Quick Reference, GC32-1729 IBM TotalStorage Productivity Center for Data for Databases User's Guide, GC32-1730 IBM TotalStorage Productivity Center for Data Messages, GC32-1731 To order publications, access the IBM Publications Center on the Web (note publication order number) by visiting http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss, by calling IBM Direct Publications: 1-800-879-2755 (US); 1-800-426-4968 (Canada), or by visiting any non-IBM bookstore.
Self study
You can access the IBM TotalStorage Productivity Center for Data V3.1 Resource library for self study. IBM Tivoli Storage Manager manuals and IBM Redbooks are useful tools for preparing to take Test 900.
IBM Tivoli Storage Redbooks

The following are Tivoli Storage related IBM Redbooks: IBM TotalStorage Productivity Center V2.3: Getting Started, SG24-6490 IBM TotalStorage Productivity Center is a suite of infrastructure management software that can centralize, automate, and simplify the management of complex and heterogeneous storage environments. It can help reduce the effort of managing complex storage infrastructures, improve storage capacity utilization, and improve administration efficiency. IBM TotalStorage Productivity Center allows you to respond to on demand storage needs and brings together, in a single point, the management of storage devices, fabric, and data. This IBM Redbook is intended for administrators and users who are installing and using IBM TotalStorage Productivity Center. It provides an overview of the product components and functions. It describes the hardware and software environment required and provides a step-by-step installation procedure. Customization and usage hints and tips are also provided.
24
IBM Tivoli Storage Resource Manager: A Practical Introduction, SG24-6886 Storage growth continues to accelerate, and the cost of disk can approach 80% of total system hardware costs. Yet, the storage in most businesses is typically only about 50% used. How can you take control of your storage assets to render utilization more efficient and make the most of your storage dollars? The new product IBM Tivoli Storage Resource Manager helps you discover, monitor, and create enterprise policies for your file systems and databases. You will discover where all your storage is going, and be able to act intelligently on this information. Application availability is improved because you will have an early warning when file systems are running out of space. If you are thinking about server consolidation, you can use IBM Tivoli Storage Resource Manager to help efficiently utilize your accumulated storage resources. This IBM Redbook shows how to install, configure, and protect the IBM Tivoli Storage Resource Manager environment; how to create policies; how to define automated actions like scripts or SNMP events when policies are violated; and how to produce detailed, meaningful, storage reports. This book is intended for those who want to learn more about IBM Tivoli Storage Resource Manager and those who are about to implement it. Exploring Storage Management Efficiencies and Provisioning Understanding IBM TotalStorage Productivity Center and IBM TotalStorage Productivity Center with Advanced Provisioning, SG24-6373 This IBM Redbook provides an overview of the solution offerings IBM TotalStorage Productivity Center and IBM TotalStorage Productivity Center with Advanced Provisioning. It presents an overview of the product components and functions, explaining the architecture and showing the use of storage provisioning workflows. This book is intended for those who want to learn more about IBM TotalStorage Productivity Center, IBM TotalStorage Productivity Center with Advanced Provisioning, and IBM TotalStorage Provisioning Manager.
IBM Publications Center

To order publications, please access the IBM Publications Center on the Internet: http://www.ibm.com/shop/publications/order Or, call IBM Direct Publications: 1-800-879-2755 (US) 1-800-426-4968 (Canada) or a bookstore
25
1.4.3 Other information

IBM TotalStorage Productivity Center for Data is a premier Java and Web-based solution designed to help you identify, evaluate, control, and predict your enterprise storage management needs. Productivity Center for Data supports today's complex heterogeneous environment, including Direct Access Storage (DAS), Network Attached Storage (NAS), and Storage Area Network (SAN) storage, including intelligent disk subsystems. Productivity Center for Data supports leading databases and provides chargeback capabilities based on storage usage. Detailed information and documentation about IBM TotalStorage Productivity Center for Data V3.1 can be found at the Web site listed below. Some of the documents contained on this Web page include Brochures, Whitepapers, Resource Guides, and links to additional information. Reading these documents in addition to hands-on experience and skills with the product will help prepare a candidate for certification testing. This link will route you to the product information page: http://www-1.ibm.com/servers/storage/software/center/data/index.html
26
Chapter 2.
Overview of IBM TotalStorage Productivity Center for Data

In this chapter, we introduce IBM TotalStorage Productivity Center for Data concepts. You will find a high-level technical introduction to TotalStorage Productivity Center for Data, its architecture, and base components. We discuss these topics: Introduction to IBM TotalStorage Productivity Center for Data Product features Architecture Supported environments for Version 3 Release 1
27
2.1 Introduction to IBM TotalStorage Productivity Center for Data

TotalStorage Productivity Center for Data is designed to provide a comprehensive storage resource management (SRM) solution for heterogeneous storage environments across the enterprise. It includes enterprise-wide reporting and monitoring, policy-based management, and automated capacity provisioning for direct-attached storage (DAS), network-attached storage (NAS), and storage area network (SAN) environments. IBM TotalStorage Productivity Center for Data enables administrators to identify, manage, control, and predict storage usage. It also provides file system and database management and reporting on storage capacity and growth. TotalStorage Productivity Center for Data provides over 300 enterprise-wide reports, monitoring, alerts, policy-based action, and file system capacity automation in the heterogeneous environment. It allows you to create customized reports as well. The standardized reports provide information about file systems, databases, and storage infrastructure. These reports provide the storage administrator information about: Assets Availability Capacity Usage Usage violation Backup TotalStorage Productivity Center for Data helps improve capacity utilization of file systems and databases and helps add intelligent data protection and retention practices. TotalStorage Productivity Center for Data performs the following functions: Discovers and monitors disks, partitions, shared directories, and servers Monitors and reports on capacity and utilization across platforms to help you to identify trends and prevent problems Monitors storage assets associated with enterprise-wide databases and issues notifications of potential problems Provides a wide variety of standardized reports about file systems, databases, and storage infrastructure to track usage and availability Provides file analysis across platforms to help you to identify and reclaim space used by non-essential files
28
Provides policy-based management and automated capacity provisioning for file systems when user-defined thresholds are reached Generates invoices that charge back for storage usage on a departmental, group, or user level The functions that are available with the Data Manager component of TotalStorage Productivity Center (as described below) are designed to help lower storage costs by: Improving storage utilization Enabling intelligent capacity planning Supporting application availability through computer uptime reporting and application database monitoring The architecture of IBM 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 large environments, and allows them to get the information about utilization and usage that is typically required in such environments. The information collected by TotalStorage Productivity Center for Data can help you make intelligent decisions optimizing the utilization of your open system environments. The data collected by TotalStorage Productivity Center for Data helps you understand what is really going on with the data that resides on your servers. This includes views as to 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 allows the system administrator to plan the purchase of additional capacity in a planned proactive manner rather than just reacting to being out of space.
Chapter 2. Overview of IBM TotalStorage Productivity Center for Data
29
The major components of TotalStorage Productivity Center for Data are: Data Manager The manager controls the discovery, reporting, and alert functions. It does the following: 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 created actions. 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 down time. 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 file systems 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 for performing administrative actions. 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.
30
2.2 Product features

This section describes significant features of TotalStorage Productivity Center for Data.
2.2.1 Policy-based management

TotalStorage Productivity Center for Data can enable you to define and enforce storage policies through user-defined alerts, quotas, and constraints, notifying the user by e-mail, pager, or the event log, or a systems management console for events such as when a quota has been exceeded or a constraint violated. The aim should not be just to find a problem; you need a way to fix problems. 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 trigger Tivoli Storage Manager to archive this data. This feature allows you to effectively manage your storage. Benefits include the consistent implementation of storage resource management policies across platforms, automated scheduled reporting, and automated file system extension.
2.2.2 Automatic file system extension

Through monitoring, TotalStorage Productivity Center for Data detects when a file system has exceeded a user-defined threshold and automatically extends the file system to prevent an out of space condition. When used in conjunction with an IBM Enterprise Storage Server (ESS), a LUN is created and provisioned to the file system automatically. A probe runs on agents and sends file system statistics to the server. The server compares the current file system state against the policy and invokes provisioning and extension as necessary.
2.2.3 Tivoli Storage Manager integration

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

TotalStorage Productivity Center for Data gathers and reports on disk subsystems. Information includes physical characteristics, such as the drive's manufacturer, model, serial number, capacity, and rotational speed. Also included is how that drive's storage is allocated to logical volumes, snapshot copy volumes, and free space. This feature allows users to perform the following (subject to the vendor's implementation of Storage Management Initiative Specification (SMIS)): Display the physical disks behind what the host sees as a disk drive Show the allocated and free capacity of subsystems in the network List subsystem volumes that have been allocated but are not in use Show which hosts have access to a given subsystem volume Show which hosts have access to a given disk drive (within the subsystem) Show which subsystem volumes (and disks) a host has access to Obtain SAN Volume Controller reporting
2.2.5 NAS support

TotalStorage Productivity Center for Data can enable storage administrators to monitor, report on, and manage NAS resources. TotalStorage Productivity Center for Data is designed to provide a universal view of direct-attached and network-attached storage, from a file system or application perspective. For Network Appliance files, TotalStorage Productivity Center for Data monitors, reports on, and manages physical disk information, such as 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 (file system) 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.
2.2.6 Advanced provisioning

TotalStorage Productivity Center for Data is an integral piece of the TotalStorage Productivity Center with Advanced Provisioning solution and is designed to allow you to automate capacity provisioning capabilities through automated workflows.
32
2.2.7 Comprehensive reporting

With a wide variety of predefined reports, from summaries to detailed reports on storage assets, you can optimize storage, minimize down time, and streamline storage management.
2.2.8 Monitoring and alerts

TotalStorage Productivity Center for Data monitors storage assets and discovers newly added storage resources on your network with centralized administration from a Web-based graphical user interface. TotalStorage Productivity Center for Data allows you to set thresholds and alerts so that you can be notified by e-mail, an SNMP trap, or a UNIX or Microsoft Windows Event log when certain conditions occur.
2.2.9 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.
2.2.10 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.
2.3 Architecture
IBM TotalStorage Productivity Center for Data has four major architecture components: the server, scheduler, repository, and agent. There is also a Common Information Model/Object Messaging (CIM/OM) component used for collecting data from storage subsystems, such as the IBM Enterprise Storage Server and DS4000.
33
Figure 2-1 on page 34 illustrates an architectural overview for IBM TotalStorage Productivity Center for Data.
Figure 2-1 TotalStorage Productivity Center for Data Architecture overview
The left section of Figure 2-1 on page 34 shows different workstations that are running user interface (UI) components for accessing TotalStorage Productivity Center Server. We have two types of clients available: the first is a Web-based client and the second is a regular fat Java client. The Managing Servers section in the middle illustrates TotalStorage Productivity Center Servers that are necessary from an architectural point of view. The Web Server will run 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 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.
34
The Managed Resources section on the right side illustrates machines that are running the TotalStorage Productivity Center for Data agent component. These are the systems from which the TotalStorage Productivity Center Server gathers its information. This should be done on a regular and scheduled basis, to keep the information in the repository as current as possible. The architectural diagram 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 different methods used to collect information from multiple systems to give an administrator the necessary views on the environment, for example: Agent Manager with its registry repository Software clients (agents) Standard interfaces and protocols (for example, Simple Network Management Protocol) Common Information Model (CIMOM agent) Repository
2.3.1 Data flow

Figure 2-2 on page 36 represents sample data flow between IBM TotalStorage Productivity Center and its main components, such as agents, Data Manager Web UI, CIMOMs, and it also shows the interaction point with IBM TotalStorage Provisioning Manager. TotalStorage Productivity Center for Data can be integrated as one solution with TotalStorage Productivity Center for Disk and TotalStorage Productivity Center for Fabric. These applications share the same architectural elements, such as Tivoli Common Agent installed on appropriate servers and Agent Manager, that authenticates and secures connections between server components, such as Data Manager and particular agents. IBM TotalStorage Provisioning Manager is an application in which the IBM vision for On Demand Business has, at its heart, the automation and provisioning strategies provided by such products as IBM Tivoli Provisioning Manager. The IBM TotalStorage Productivity Center with Advanced Provisioning offering is designed to allow assisted capacity provisioning capabilities through automated workflows. Storage provisioning using IBM TotalStorage Productivity Center with Advanced Provisioning helps you to save time and avoid human error by automating the many steps involved in allocating storage to an application or user. Provisioning automates the way IT resources are made available. IBM Tivoli Provisioning Manager helps clients significantly reduce the time it takes to
35
accomplish complex IT tasks, while eliminating the risk of human error by automating complex IT processes using best practices.
Figure 2-2 Data flow
2.3.2 Schema of interactions

On Figure 2-3 on page 37, you can find the high level architecture and agent interaction in the IBM TotalStorage Productivity Center for Data. We show protocols that are used to monitor and manage storage subsystems. The three layers in the graphic represent the various component areas, such as the server, the agent, and the proxy agents. The scheduler service is running on the server component.
36
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
SNMP, NFS, CIFS, NCP

LUM
Application Server
File and Print Server
Enterprise Storge Server
Figure 2-3 High level architecture
2.3.3 Data Manager - server

The server is the center of Data Managers architecture and directs all of the activities related to the monitoring performed on the monitored agent computers and the reporting performed on the client GUI computers. The Server interacts with the enterprise repository, job scheduler, agents, and agent manager (for authorization and authentication of agents). Data Manager receives information from the agents and saves that information in the repository. The repository is where all of your storage information and usage statistics are stored. All agent and user interface access to the central repository is done through a series of calls and requests made to the server. The Data Manager server consists of two components: the Enterprise Repository and the Job Scheduler.
37
Enterprise Repository
Data Manager 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.
2.3.4 User interface

The user interface (UI) enables users to request information and then generate and display reports based on that information. The client UI component of Data Manager provides the user interface for: Monitoring your storage Defining and receiving alerts on storage events Generating and viewing reports As Data Manager monitors your storage across your enterprise, it accumulates a repository of knowledge about your storage assets and how they are used. You can use the reports provided in the user interface view and analyze that repository of information from different perspectives to gain insight into the use of storage across your enterprise. 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.
38
2.3.5 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 should be monitored. Data Manager uses a Common Information Model 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. This allows an agent to: Detect low-level problems, such as defects in the hardware containing the storage information Keep track of information, such as the uptime and downtime of the machine on which it is running Return information to the server from the scans and probes Agents receive jobs to run from a server's scheduling service and then contact the server for the job definition. Once this has successfully completed, 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 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. 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 you want to scan are visible. You do not install agents to the NAS filers themselvesrather, you install them to Windows, UNIX, and Linux machines that have access to those NAS filers (for example, install agents to Windows machines that can access your NAS filers, or install agents to UNIX/Linux machines that have imports for the file systems within the NAS filers). See the IBM TotalStorage Productivity Center for Data Installation and Configuration Guide, GC32-1774 for more information.
39
For Microsoft Cluster Server (MSCS) support, install and license an agent on every cluster node machine.
2.3.6 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; without it, you cannot register Data Manager server or any agents. Registration is password-protected, with 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 (either remote or local). 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.
2.3.7 Integration points with TEC and IBM Tivoli Storage Manager
In this section, we describe IBM TotalStorage Productivity Center for Data integration points with IBM Tivoli Enterprise Console (TEC) and IBM Tivoli Storage Manager. The integration with IBM Tivoli Enterprise Console is done through the alert notification facility.
Alert notification
The main purpose of Data Manager's alerting facility is to alert you to storage-related events that occur within your environment. Once you have defined the events or conditions for which you want to be alerted, you can let Data Manager monitor your storage automatically.
40
SNMP
For users planning to make use of Data Manager's SNMP trap alert notification capabilities, an SNMP Management Information Base (SNMP MIB) is included in the server installation. The SNMP MIB can be found in a file in the default Data Manager installation directory: For Windows: \Program Files\IBM\TPC\Data\snmp\tivoliSRM.MIB For UNIX/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 HP Openview). This will allow 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, perform: For Windows: a. Right-click My Computer. b. Click Manage. c. Click Services. For UNIX/Linux: a. For information about whether SNMP is running and if so, on which port, check in /etc/services. The default community name used by Data Manager to forward SNMP traps is
public. Integration with Tivoli Enterprise Console

IBM TotalStorage Productivity Center for Data can use the Event Integration Facility (EIF) to send messages to the IBM Tivoli Enterprise Console (TEC). This can allow TEC to consider IBM TotalStorage Productivity Center for Data alerts in causal analysis for problems. TEC is added as a destination for alerts, in addition to Simple Network Management Protocol (SNMP) Trap and Windows Event Log. The event definitions are specified in the tivoliSRM.baroc file (provided by Data Manager), which is provided on the Data Manager installation CD. It must be loaded to the active rule base running on the TEC server. Based on that, the TEC administrator can write its own correlation and automation rules for events sent by Data Manager. You have to provide the TEC server name and the TEC port to start sending events to the TEC server.
41
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 2-4 on page 42 for an example of the Alert Disposition window.
Figure 2-4 Alert Disposition window
Integration with Tivoli Storage Manager

Integration between IBM TotalStorage Productivity Center for Data and IBM Tivoli Storage Manager has two capabilities: The definition of a constraint violation is a means by which an administrator can enforce a request to have IBM Tivoli Storage Manager archive or back up the n largest violating files. Another kind of constraint violation is to define
42
acceptable and unacceptable uses of storage systems. For example, a constraint can be defined to prohibit storing MP3 files on a file server. Productivity Center for Data currently reports on the n largest of the files, which violate the constraint (where n is configured by the administrator). Even the regularly run file reports can be modified to allow administrators to archive or back up selected files directly as an outcome of the reports. These file reports can identify, for example, a file system's largest files, orphaned files, and duplicate files. A storage administrator can use this feature to quickly free storage by archiving and deleting selected files. These integration point variants can provide support for: IBM Tivoli Storage Manager archive with the option of deleting the file after successful archive IBM Tivoli Storage Manager incremental and selective backups The results of the IBM Tivoli Storage Manager backup-archive commands are viewable through the graphical user interface (GUI). In the case of constraints configured to archive-backup violating files, the results are included in the agent scan job logs (scans are responsible for enforcing constraints). In the case of file report driven archive-backup operations, a new type of job (archive-backup job) is created. The results of the backup operations in this case are found in archive-backup job logs.
2.3.8 Tivoli Common Agent Services

Tivoli Common Agent Services provides a way to deploy multiple agent code across multiple user machines or application servers throughout your enterprise. The deployed agent code collects data from and performs operations on managed resources on behalf of a management application. The Tivoli Common Agent Services provides an Agent Manager that provides authentication, authorization, and maintains a registry of configuration information about the agents and resource managers in your environment. The Resource Manager is a part of the Tivoli Common Agent Services and is the server component of products that manage subagents deployed on the common agent. The Tivoli Common Agent Services also provides common agents to act as a container to host product subagents and common services. The common agent provides remote deployment capability, shared machine resources, secure connectivity, and a single-entry point on the client computers on which the agents reside.
43
shows all these components and how they interact.
Data Server
Resource Manager
Device Server
Resource Manager
Agentmanager RegistrationService RecoveryServices

Ports: 9511 - registration 9512 - authentication 9513 - updates
IBMCDB
Holds the Registration Of all Agents And Resource Managers
Ports: 80 recovery 9513 alternate for recovery
SubAgent Data
SubAgent Fabric
CommonAgent
Application Server with Agent
Figure 2-5 Common Agent Services infrastructure
In Figure 2-5 on page 44, you can see a simplified diagram showing the two most important services 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. A more detailed list of all the ports and their relationship can be found in the IBM TotalStorage Productivity Center for Data Installation and Configuration Guide, GC32-1774.
2.3.9 Role-based Administration

This section describes the Role-based Administration you should consider when installing Data Manager. TotalStorage Productivity Center and its Data Manager component support mainly two types of users, the operator and the administrator users. The type of user determines how they use Data Manager. This is implemented by introducing a mapping between the roles within TotalStorage Productivity Center and the groups that are in place at the operating system level of your TotalStorage Productivity Center server.
44
Operator users: These users view the data collected by Data Manager. They can create, generate, and save reports. Data Manager administrators: These users can: Create, modify, and schedule pings, probes, and scans Create, generate, and save reports Perform administrative tasks and customize the Data Manager environment Create groups, profiles, quotas, and constraints Set alerts
2.4 Supported environments for Version 3 Release 1

For a list of the supported systems, platforms, and other related operating system information, you should use the following links to ensure you have the latest information: TotalStorage Productivity Center Version 3 Release 1 Supported Product List - IBM Storage http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002800 TotalStorage Productivity Center Version 3 Release 1: 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 1 Platform Support: Agents, CLI and GUI http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002814 TotalStorage Productivity Center Version 3 Release 1 Platform Support: Managed Database Support http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813
Generic SMI-S array reporting and SNIA CTP certification

This feature enables Data Manager to discover, monitor, enforce policies, alert upon, and report upon any disk array subsystems whose providers are CTP certified by SNIA for SMI-S 1.0.2 and SMI-S 1.1. Data Manager supports basic reports for any vendors disk subsystem that has been SNIA-CTP certified.
45
Support for disk array subsystems includes reports that show information gathered only through SMI-S, including subsystem manufacturer, model, LUNs, StoragePools, disk drives (for providers that support the disk drive subprofile), and HBA Port WWN to LUN assignments (for providers that support the LUN masking and mapping subprofile).
Prerequisite software to be installed

The Prerequisite Software Installer is provided to help you install the prerequisite software: DB2 Version 8.2 with Fix Pack 7a Agent Manager Version 1.2 (Agent Manager Version 1.1 is still supported.)
Tivoli Common Agent Services

Tivoli Common Agent Services supported levels are: The Agent Manager is now installed as a prerequisite before the product installation itself. The database for the Agent Manager supports only DB2 UDB. Agent Manager Version 1.1 and Version 1.2 are supported. When you install the Agent Manager, you can elect to upgrade to Version 1.2 or stay at Version 1.1.
WebSphere Application Server

The version of WebSphere Application Server supported is 5.1.1.3 (both the full version and the embedded version).
46
Chapter 3.
Planning
This chapter describes the planning part of IBM TotalStorage Productivity Center for Data 3.1 implementation. We describe system requirements, product documentation, and the implementation process of IBM TotalStorage Productivity Center for Data V3.1. This chapter provides: What you should know about the planning section of the test objectives Summary of changes for IBM TotalStorage Productivity Center for Data Version 3.1 IBM TotalStorage Productivity Center for Data V3.1 system requirements and supported systems Pre-installation steps for Windows Analyzing and defining environment requirements Customer support
47
3.1 What you should know about the planning section of the test objectives
We discuss the first section of the IBM TotalStorage Productivity Center for Data 3.1 Implementation Certification Test objectives, which is planning. At the end of this chapter, you should be able to complete the following tasks: Analyze environment. Reporting requirements. Recommend a database. Verify that ports (TCP/IP) are available. TotalStorage Productivity Center for Data server sizing. Assemble resources to be used in projects. Identify integration points with other products. Create diagram environment. Create task list and project plan. Agent distribution methodology. Review product documentation (Release Notes). Visit support Web site to ensure latest product enhancements.
3.2 Summary of changes for IBM TotalStorage Productivity Center for Data Version 3.1
This section summarizes changes that have been made to the IBM TotalStorage Productivity Center for Data product. There are a lot of new features that were not available in the previous version, IBM Tivoli TotalStorage Productivity Center 2.1 You should be familiar with them. We provide only the list of new features of the IBM TotalStorage Productivity Center for Data 3.1. You can find all newly supported operating systems listed in Deployment Guide Series: TotalStorage Productivity Center for Data, SG24-7140.
3.2.1 Technical changes for Version 3 Release 1

TotalStorage Productivity Center V3.1 offers: A single, integrated package with a new topology viewer, providing an end-to-end view of the Storage Area Network (from hosts to physical disks). A simple, easy to install package with management server support added for IBM AIX 5L V5.3, and integrating IBM DB2 as the management server database.
48
The server components of IBM TotalStorage Productivity Center can now be installed on: Microsoft Windows 2003 AIX 5L V5.3 (p5 supported) Linux Red Hat 3.0 on IBM System x Performance management support for the IBM TotalStorage DS4000 family and additional performance support for select IBM TotalStorage, Brocade, Cisco, and McData fabric switches and directors. Role-based task authentication that assists with implementing storage management that conforms to government initiatives. Support for managing IBM TotalStorage 3584 and limited support for IBM TotalStorage Enterprise Automated 3494 tape libraries. Support for third-party disk array systems that include Storage Management Interface Specification (SMI-S) Providers certified by the SNIA Conformance Test Program (CTP) to be SMI-S 1.02 or SMI-S 1.1 compliant. This support includes storage provisioning, as well as asset and capacity reporting. Consolidated and enhanced device discovery and control through CIMOM. All CIMOM related information gathered during CIMOM discovery are shared by all TotalStorage Productivity Center components. Consistent reporting capabilities (scheduled and ad hoc). The scheduling capabilities of TotalStorage Productivity Center for Data have been extended to all components. Consolidated message logging. Data export capabilities (HTML and CSV). Single set of services for consistent administration and operations: Policy definitions. Event handling. Resource groups. New command-line interface tpctool for configuration, fabric and disk management, and performance reporting. TotalStorage Productivity Center for Fabric adds support for SMI-S-based fabric, collecting performance statistics from IBM and third-party SAN fabrics. TotalStorage Productivity Center for Fabric is designed to provide an extended graphical topology view of your storage area network that displays the hosts, SAN fabric and storage, showing the SAN connectivity and its availability and also the fabric performance metrics and the status of the ports on the SAN fabric.
Chapter 3. Planning
49
TotalStorage Productivity Center V3.1 provides the following support for any disk subsystems (including non-IBM devices) that are SNIA SMI-S 1.0.2 or 1.1 compliant (for example, SNIA CTP provider certified). The support provided for these SMI-S compliant subsystems will include those functions enabled by support for the required profiles of the SMI-S standard. Typically, that will include: Discovery of CIMOMs and storage subsystems (through SLP). Reporting on subsystem asset and capacity data (with details on storage subsystems, disk groups, disks, storage pools, and volumes). Monitoring. Provisioning (volume creation and volume mapping/masking to host server). Performance metrics for storage subsystem ports, subsystem volumes, and top level storage Computer Systems (including overall performance metrics for the storage device). It should also be noted that IBM will rely on the testing and certification being performed through SNIA for SMI-S compliance. The anticipated list of non-IBM disk subsystems that TotalStorage Productivity Center V3.1 will support through SMI-S compliance for the functions listed here include: EMC Symmetrix EMC Clariion Engenio subsystems HDS Thunder 9500V HDS Lightning 9900V HPQ XP 512, XP 1024 HPQ Storage Works Virtual Array family
For a complete list of third-party device support of SMI-S, consult the SNIA Web site: http://www.snia.org/ctp
3.2.2 Functions no longer provided in TPC V3.1

The following is a list of TotalStorage Productivity Center items in prior releases that are not in TotalStorage Productivity Center V3.1: Workflow integration of TotalStorage Productivity Center with Tivoli Provisioning Manager is not supported. ED-FI or SAN error predictor functionality is not supported in this release.
50
TotalStorage Productivity Center for Replication is not integrated with the V3.1 components (TotalStorage Productivity Center for Data, TotalStorage Productivity Center for Disk, and TotalStorage Productivity Center for Fabric). Prerequisite Software Installer. Suite Installer. ICAT installation. Tivoli NetView installation, uninstallation, and upgrade. IBM Director base. IIBM TotalStorage Productivity Center for Data supported its database repository on Oracle, SQL Server, and Cloudscape in Version 2.x. These databases are not supported in TotalStorage Productivity Center V3.1. Installing Simple Network Management Protocol (SNMP) service with community name of public and Management Information Base (MIB) files is no longer necessary. iSCSI support in Fabric Manager.
3.3 IBM TotalStorage Productivity Center for Data V3.1 system requirements and supported systems
Before deploying IBM TotalStorage Productivity Center for Data V3.1 (also called Data Manager), you may need to analyze customer environments, under IBM TotalStorage Productivity Center for Data 3.1 system requirements. In this section we provide information about IBM TotalStorage Productivity Center for Data V3.1 system requirements and prerequisites, for example, Data Manager Repository considerations and storage subsystem support (but you do not need to collect all the information about storage subsystems; you do not need to know Enterprise Storage capacity).
3.3.1 Hardware prerequisites

This section lists the minimum prerequisites. In our ITSO residency, we installed all TotalStorage Productivity Center components on a single computer.
Chapter 3. Planning
51
For Windows and Linux on Intel, IBM System x server, or other Intel technology-compatible platforms, the hardware requirements are: Server Dual Pentium 4 or Xeon 2.4 GHz or faster processors 4 GB of RAM Network connectivity Agent Pentium 400 MHz processor, or above 256 MB of RAM For AIX on IBM System i and IBM System p servers: Server Machine - Minimum 1.0 GHz processor 4 GB of RAM Network connectivity Agent 400 MHz processor, or above 256 MB of RAM
3.3.2 Disk space requirements

The Windows requirements are: Server 4 GB of available disk space for the code and up to approximately 80 GB of hard disk space for databases 500 MB in the Windows temporary directory Agent 100 MB of hard disk space The UNIX or Linux requirements are: Server 80 GB of hard disk space 500 MB in /tmp and 1.3 GB in /opt Agent 100 MB of hard disk space
52
Linux on IBM System z server requirements Agent 100 MB of hard disk space Note: To determine the installed memory and processor type on a given Windows machine, display system properties in the GUI by right-clicking My Computer and selecting Properties. Use the uname command to determine machine information about a given AIX machine.
3.3.3 Software prerequisites

Table 3-1 shows the platforms supported by TotalStorage Productivity Center server components. We have included information for all the TotalStorage Productivity components for completeness and future planning considerations.
Table 3-1 Platform support for Data server, Device server, GUI, and Agent Manager Platform Data server, Device server, database schema (DB2), and CLI No No Yes GUI Agent Manager V1.2 (install Fix Pack 2, even if you can optionally use the Agent Manager you installed with V2.3) Yes No Yes
Windows 2000 Advanced Server Windows 2000 Datacenter Windows Server 2003 Standard Edition 32-bit or 64-bit Windows Server 2003 Enterprise Edition 32-bit or 64-bit Red Hat Enterprise Linux AS Version 3.0 IBM System x server Red Hat Enterprise Linux AS Version 3.0 IBM System p on POWER5
No No Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Chapter 3. Planning
53
Platform
Data server, Device server, database schema (DB2), and CLI No
GUI
Agent Manager V1.2 (install Fix Pack 2, even if you can optionally use the Agent Manager you installed with V2.3) No
Red Hat Enterprise Linux AS Version 3.0 IBM System i on POWER5 United Linux 1.0 IBM System x server United Linux 1.0 IBM System z server SUSE Linux Enterprise Server 8 IBM System p on POWER4 System z server SUSE Linux Enterprise Server 9 IBM System x server, IBM System p on POWER5, IBM System i server on POWER5, and IBM System z server (Data agent only) IBM AIX 5L V5.1 (32-bit) IBM AIX 5L V5.1 (64-bit) IBM AIX 5L (32-bit) IBM AIX 5L (64-bit) IBM AIX 5L V5.2 (32-bit) IBM AIX 5L V5.2 (64-bit)
No
No No No
No No No
No No No
No
No
No
No No No No No No
No No No No No No
Yes Yes Yes Yes Yes Yes
54
Platform
Data server, Device server, database schema (DB2), and CLI Yes (with AIX 5300-01 maintenance level and APAR IY70336)
GUI
Agent Manager V1.2 (install Fix Pack 2, even if you can optionally use the Agent Manager you installed with V2.3) Yes (32-bit and 64-bit)
IBM AIX 5L Version 5.3 (32 bit)
Yes (with AIX 5300-01 maintenance level and APAR IY70336) No No No
Solaris 8 Solaris 9 HP-UX 11 and 11i
No No No
Yes Yes No
Table 3-2 shows the platforms supported to install and deploy Data agents and Fabric agents. For completeness and future upgrade planning, we have included the information for Fabric agents as well. Important: Data agents and Fabric agents at Version 2.x are supported by IBM TotalStorage Productivity Center V3.1 managers.
Table 3-2 Platform support for Data agent and Fabric agent Platform Windows 2000 Advanced Server Windows 2000 Datacenter Windows Server 2003 Standard Edition 32-bit or 64-bit Windows Server 2003 Enterprise Edition 32-bit or 64-bit Red Hat Enterprise Linux AS Version 3.0 IBM System x server Red Hat Enterprise Linux AS Version 3.0 IBM System p on POWER5 Red Hat Enterprise Linux AS Version 3.0 IBM System i on POWER5 United Linux 1.0 IBM System x server United Linux 1.0 IBM System z server Data agent and Fabric agent Yes Yes Yes Yes Yes Only Data agent Only Data agent Only Data agent Only Data agent
Chapter 3. Planning
55
Platform SUSE Linux Enterprise Server 8 IBM System p on POWER4 IBM System z server SUSE Linux Enterprise Server 9 IBM System x server, IBM System p on POWER5, IBM System i on POWER5, and IBM System z server SUSE Linux Enterprise Server 9 IBM System x server, IBM Systgem p on POWER5, IBM System i on POWER5, and IBM System z server IBM AIX 5L V5.1 (32-bit)
Data agent and Fabric agent Only Data agent
Only Data agent
Data agent (all) Fabric agent (IBM System x server only) Yes with AIX 5100-05 maintenance level Yes in compatibility mode with AIX 5100-05 maintenance level Yes in compatibility mode with AIX 5100-05 maintenance level Yes in compatibility mode with AIX 5100-05 maintenance level Yes with AIX 5200-02 maintenance level Yes in compatibility mode with AIX 5200-02 maintenance level Yes with AIX 5300-01 maintenance level and APAR IY70336 Yes Yes
IBM AIX 5L V5.1 (64-bit)
IBM AIX 5L (32-bit)
IBM AIX 5L (64-bit)
Solaris 8 Solaris 9
56
Platform HP-UX 11 and 11i NetWare 5.1, 6.0, and 6.5 VMWare ESX environment (Data agent tolerance support only; does not include VMWare logical reporting enhancements) MSCS Clustering Windows 2000 Advanced Server MSCS Clustering Windows 2000 Datacenter MCSC Clustering Windows 2003 Advanced Server MSCS Clustering Windows 2003 Datacenter AIX Volume Manager VERITAS Volume Manager on Solaris and HP-UX IBM NAS Gateway 500 Network Appliance NAS AIX JFS VERITAS File System (VxFS) on Solaris
Data agent and Fabric agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent Only Data agent
3.3.4 Novell NetWare considerations

To use the Data Manager with NetWare servers, you must install the agent on a Windows computer where the Novell NetWare client is located. The Data Manager performs discovery and scans from these Windows computers using NetWare calls. When the agent is installed on a Windows computer, the agent first determines whether a NetWare client is installed. If a NetWare client is installed, the following steps occur: The agent performs an initial probe and requests a list of the NDS trees from the NetWare client (the NDS trees that are accessible to that agent). Because a NetWare client is installed, you do not need special NetWare permissions to generate a list of your NDS trees. However, the Data Manager requires permissions to the NDS trees when performing discovery and scan jobs of those trees. The agent reports the list of NDS trees to the server. Before you run a discovery or scan job, you must configure login IDs and passwords for the NDS trees in the Administrative Services Configuration node of the GUI.
Chapter 3. Planning
57
3.3.5 NAS environment considerations

This section contains the requirements for installing and running the Data Manager within an NAS environment.
Agent requirements
When installing the Data Manager in an NAS environment, the agent must be installed on a machine that has access to the NAS filers within your environment that you want to monitor: Windows The agent that is logging into 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 different domain from the NAS filer, the agent scans the NAS filer if the domain of the agent computer is a "trusted domain" by the domain of the NAS filer. UNIX and Linux The agent computer must import the NAS filer's exports as NFS mounts (or automounts on Solaris). 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.
3.3.6 Databases supported

At time of writing, we used the information from the following Web site as a reference: http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813
3.3.7 Data Manager database repository

Data Manager stores information about storage assets in the centralized repository. The repository is organized into a series of relational database tables and is accessed by Data Manager using Java Database Connectivity (JDBC). The Data Manager repository is supported only on the following database: DB2
58
Enterprise Server Edition Version 8.2 with Fix Pack 7a or higher is supported for local and remote installation. When you install IBM TotalStorage Productivity Center, a single, shared database instance is created on DB2 for the Data server and Device server. The default database name is TPCDB.
3.3.8 Agent Manager database repository

The Agent Manager repository is supported only on the following database; DB2 Enterprise Server Edition Version 8.2 with Fix Pack 7a or higher is supported for local and remote installation. There is only one database instance created for IBM TotalStorage Productivity Center on DB2. The Agent Manager repository uses its own database. The default name of this database is IBMCDB. It is possible to use only one database, IBMCDB, for both repositories, but we do not recommend this configuration. Note: We recommend that you install a single instance of IBM DB2 UDB Enterprise Server Edition Version 8.2 with fix pack 7a or higher as your repository for both the Agent Manager and IBM TotalStorage Productivity Center.
3.3.9 SMS or DMS tablespace type

At installation time, you can specify whether the DB2 database is system-managed space (SMS) or database-managed space (DMS). In SMS, the file system manager for the operating system allocates and manages the space where the table is stored. The following are some of the advantages of an SMS tablespace: Space is not allocated by the system until it is required. Creating a database requires less initial work, because you do not have to predefine containers. A container is a physical storage device and is assigned 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. We recommend you select SMS.
Chapter 3. Planning
59
The following are the advantages of a DMS tablespace: 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 is allowed by the operating system. If all table data is in a single tablespace, a tablespace can be dropped and redefined with less overhead than dropping and redefining a table. In general, a well-tuned set of DMS tablespaces outperform SMS tablespaces. We recommend you select the SMS tablespace format.
3.3.10 Database Migration Utility

If you have data that you want to migrate from IBM TotalStorage Productivity Center V2.x to V3.1, you can run the Data Migration Utility after you install IBM TotalStorage Productivity Center. For information about the Data Migration Utility, see the IBM TotalStorage Productivity Center Flash at this Web site: http://www.ibm.com/servers/storage/support/software/tpc
3.3.11 Data agent monitored databases

The Data agent can monitor these Relational Database Management Systems (RDBMSs): DB2 7.2 - 32-bit only DB2 8.1 - 32-bit or 64-bit DB2 8.2 - 32-bit or 64-bit Microsoft SQL Server 7.0 Microsoft SQL Server 2000 Oracle 8i Oracle 9i Oracle 10g Sybase
60
3.4 Pre-installation steps for Windows

The prerequisite components for IBM TotalStorage Productivity Center V3.1 are: IBM DB2 UDB Enterprise Server Edition V8.2 Fix Pack 7a or higher Agent Manager 1.2, 1.2.2, or later. Agent Manager V1.1 is not supported with TotalStorage Productivity Center V3.1.
3.4.1 Installable components

When you install TotalStorage Productivity Center V3.1, you are no longer prompted to select product components such as TotalStorage Productivity Center for Data as was the case with TotalStorage Productivity Center V2. The installable components available with TotalStorage Productivity Center V3.1 are: Database schema Data server Device server Graphical User Interface (GUI) Command Line Interface (CLI) Data Agent Fabric Agent Tip: We recommend that you install the Database Schema first. Then, install the Data server and Device server in a separate step. If you install all the components in one step, if any part of the installation fails for any reason (for example, space or passwords), the installation suspends and rolls back, uninstalling all the previously installed components.
3.4.2 Order of component installation

The components are installed in the following order: 1. DB2 2. Agent Manager 3. TotalStorage Productivity Center components
3.4.3 Server recommendations

The IBM TotalStorage Productivity Center for Data server component acts as a traffic controller for directing information and handling requests from the agent and UI components installed within an environment. You need to install at least one server within your environment. We recommend that you do not manage
Chapter 3. Planning
61
more than 1000 agents with a single server. If you need to install more than 1000 agents, you should install an additional server for those agents to maintain optimal performance.
3.4.4 Installation port requirements

IBM TotalStorage Productivity Center uses TCP/IP ports for communication, as shown in Table 3-3. These ports must be opened and available for use. If there is a firewall between the Agent Manager, the agents, and the resource managers in your deployment, you must open the ports for TCP traffic as indicated in the table.
Table 3-3 Port requirements Component Data server Device server Common Agent 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) Server perspective Inbound/Outbound Inbound/Outbound Session Initiator=Yes Outbound Session Initiator=No Inbound Session Initiator=Yes Inbound and Outbound Firewall port 9549 9550 9510 9511 Session Initiator=No Inbound Session Initiator=Yes Outbound Session Initiator=No Inbound and Outbound Agent perspective
9512
Session Initiator=No Inbound
9513
Session Initiator=Yes Outbound
9514 9515
Local to Server Local to Server
62
Component CIMOM HTTP CIMOM HTTPS Agent Recovery Service
Server perspective
Firewall port 5988 5989
Agent perspective
Session Initiator=No Inbound Session Initiator=Yes Outbound
80
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 Session Initiator=No Inbound and Outbound
Push UNIX
SSH(22)
Push Windows
Session Initiator=Yes Outbound Session Initiator=Yes Outbound Session Initiator=Yes Outbound Session Initiator=Yes Inbound Session Initiator=Yes Inbound Session Initiator=Yes Inbound
NetBIOS sessions service (139) RSH (514)
Push UNIX
Push UNIX
REXEC (512)
Push UNIX Push All
601 High ports 3000+ TPC for Data server 2078 162 427 Session Initiator=No Inbound and Outbound
Push All SNMP Listener Port SLP
If you want to choose a port other than the default 9510 for Common Agent communication, make sure that the port you choose, and ports above it, are available for use. For example, if N represents the open port you want to use, ensure that ports N+4 and N+5 are open as well.
Chapter 3. Planning
63
Note: To list ports in use, execute the following commands: For Windows:
netstat -an
For UNIX and Linux:

netstat -an | grep LISTEN
You can find the port numbers used on your system by running the following command, netstat -a or netstat -ano (to see the PID using that port, too), as shown in Figure 3-1 on page 53 and Figure 3-1 on page 53.
64
Figure 3-1 netstat -a sample
Chapter 3. Planning
65
Figure 3-2 netstat -ano sample
66
3.4.5 Supported file systems

IBM TotalStorage Productivity Center for Data supports monitoring and reporting of the following file systems: FAT FAT32 NTFS4, NTFS5 EXT2, EXT3 AIX_JFS HP_HFS VxFS UFS TMPFS AIX_OLD NW_FAT NW_NSS NF WAFL FAKE AIX_JFS2 IBM TotalStorage SAN File System REISERFS Note: File system extension is supported for JFS file systems running on AIX 5L V5.1 and VxFS file systems running on Sun Solaris 2.8. The AIX JFS2 file system is not supported.
3.4.6 Supported network file systems

Data Manager currently supports monitoring and reporting of the following networked file systems: IBM TotalStorage SAN File System 1.0 (Version 1 Release 1), from AIX 5L V5.1 (32-bit) and Windows 2000 Server and Windows 2000 Advanced Server clients IBM TotalStorage SAN File System 2.1, 2.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 File System (GPFS) V2.1 and V2.2
Chapter 3. Planning
67
3.4.7 Support for NAS/NetWare

Data Manager currently supports the monitoring of the following NAS/NetWare devices: Novell NetWare 5.1 or above NetApp Data ONTAP NAS devices other than Network Appliance Filers must meet the following criteria to be supported by this product: If scanned from a UNIX agent, an NAS device must support NFS queries. If scanned from a Windows agent, an NAS device must support Common Internet File System (CIFS) queries. An NAS device must support SNMP queries (such as sysName and sysOID). An NAS device must supply a unique sysName.
3.4.8 Disk and volume group support

Data Manager supports the monitoring of the following volume managers: VERITAS Volume Manager on Sun Solaris VERITAS Volume Manager on HP-UX AIX Logical Volume Manager (LVM) HP-UX Logical Volume Manager These volume managers enable you to create groups of logical volumes and disks. You can generate a variety of reports for these disk and volume groups. Note: Disk and volume group information appears in Asset By Computer and Asset System-wide reports.
3.4.9 Storage subsystem support

IBM TotalStorage Productivity Center V3.1 supports IBM and third-party disk systems that are Storage Management Interface Specification (SMI-S) 1.0.2 or SMI-S 1.1 compatible. This support includes storage provisioning, as well as asset and capacity reporting. TotalStorage Productivity Center V3.1 implements many of its disk, tape, and fabric management functions through exploitation of the SMI-S 1.0.2 and 1.1 levels of the standard. SMI-S 1.1 supports all of the functions of SMI-S 1.0.2 plus additional functionality (for example, performance management). These systems include, but are not limited to: IBM TotalStorage SAN Volume Controller (SVC) IBM TotalStorage Enterprise Storage Server (ESS)
68
IBM TotalStorage Disk Subsystems (DS4000, DS6000, and DS8000 Series) Disk array subsystems whose providers are CTP certified by SNIA for SMI-S 1.0.2 For the latest and complete storage subsystem support information, point your browser to the following Web site and follow the appropriate links: http://www.ibm.com/servers/storage/support/software/tpc/ For a complete list of subsystems supported through base SMI-S 1.0.2 support, view the following Web site: http://www.snia.org/ctp/certified/
3.4.10 Tape library support

IBM TotalStorage Productivity Center V3.1 supports the following tape libraries: IBM 3494 IBM 3584
3.4.11 User IDs and security

This section discusses the user IDs that are used during the installation and those that are used to manage and work with TotalStorage Productivity Center. It also explains how you can increase the basic security of different components.
User IDs
This section lists and explains the user IDs used in a TotalStorage Productivity Center environment.
Granting privileges
Grant privileges to the user ID 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.
Chapter 3. Planning
69
To manually set these privileges, follow these steps: 1. Select Start Settings Control Panel. 2. Double-click Administrative Tools. 3. Double-click Local Security Policy. 4. The Local Security Settings window opens. Expand Local Policies. Then double-click User Rights Assignments to see the policies in effect on your system. For each policy added to the user, perform the following steps: a. Highlight the policy to be selected. b. Double-click the policy and look for the 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.
Increasing user security

The goal of increasing security is to have multiple roles available for the various tasks that can be performed. Each role is associated with a certain group. The users are only added to those groups that they need to be part of to fulfill their work.
Role-based levels of users

There are mainly two levels of users within TotalStorage Productivity Center. They are an Operator user and an Administrator for each of the specific work areas in IBM TotalStorage Productivity Center (Data, Fabric, Disk, and Tape). Besides this, there is a general TotalStorage Productivity Center administrator, who can work in all four areas as an administrator and, on top of that, is a
70
so-called Superuser. This is the standard user you are working with right after installing the product. The level of these users determines how they can use the 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. Important: Security is set up by using the certificates. You can use the demonstration certificates or you can generate new certificates. We recommend that you generate new certificates when you install the Agent Manager.
Microsoft Windows domain

If you are installing the TotalStorage Productivity Center in a Microsoft Windows environment, it does not support the following Microsoft Windows domain login formats for logging into the server component: (domain name)/(username) (username)@(domain) Because TotalStorage Productivity Center does not support these formats, you must set up users in a domain account that can log into the server. Perform the following steps before you install Productivity Center for Data in your environment: 1. Create a Local Admin Group. 2. Create a Domain Global Group. 3. Add the Domain Global Group to the Local Admin Group. Productivity Center for Data looks up the SID for the domain user when the login occurs. You only need to specify a user name and password.
Chapter 3. Planning
71
3.4.12 Certificates and key files

A TotalStorage Productivity Center environment uses certificates to ensure a high level of security. The security certificates can be generated during the installation of the Agent Manager component. During the installation, key files can be generated as self-signed certificates, but you must enter a password for each file to lock it. Although you can leave the password for the Certificate Authority file blank, we do not recommend it. If you leave this password blank, a random password is generated for you during the installation process and you are then unable to unlock the Certificate Authority file. We, therefore, recommend that you enter a password for this file, which allows you to unlock the Certificate Authority file later, if needed. The default file names are: CARootKeyRing.jks (the Certificate Authority file) agentTrust.jks (the Common Agent registration file) The default directory for the key file on the Agent Manager in a Windows environment is C:\Program Files\IBM\AgentManager\certs. In a UNIX or Linux environment, the default directory is /opt/IBM/AgentManager/certs.
Agent Manager certificates

The Agent Manager comes with demonstration certificates that you can use. However, you can also create new certificates during the installation of Agent Manager. If you choose to create new files, the password that you enter as the Agent registration password is used to lock the agentTrust.jks key file. The default directory for that key file on the Windows Agent Manager is C:\Program Files\IBM\AgentManager\certs. 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 is only important if you allow the installer to create your keys, which we recommend.
3.4.13 Services and service accounts

The managers and components that belong to the TotalStorage Productivity Center are started as Windows Services. Table 3-4 on page 73 provides an overview of the most important services. To keep it simple, we did not include all the DB2 services in the table.
72
Table 3-4 Services and service accounts Element DB2 Agent Manager IBM WebSphere Application Server V5 Tivoli Agent Manager IBM Tivoli Common Agent C:\Program Files\tivoli\ep IBM TotalStorage Productivity Center for Data server IBM WebSphere Application Server V5 Fabric Manager Service name Service account db2admin LocalSystem Comment The account needs to be part of Administrators and DB2ADMNS. You need to set this service to start automatically, after the installation.
Common Agent
itcauser
Productivity Center for Data Productivity Center for Fabric
TSRMsrv1
LocalSystem
3.4.14 Starting and stopping the managers

To start, stop, or restart one of the managers or components, you use the Windows control panel. Table 3-5 shows a list of the services.
Table 3-5 Services used for TotalStorage Productivity Center Element DB2 Agent Manager Common Agent Productivity Center for Data Productivity Center for Fabric Service name Note that there are several services for db2. IBM WebSphere Application Server V5 - Tivoli Agent Manager. IBM Tivoli Common Agent C:\Program Files\tivoli\ca. IBM TotalStorage Productivity Center Data server. IBM WebSphere Application Server V5 - Device server. Service account db2admin LocalSystem itcauser TSRMsrv1 LocalSystem
Chapter 3. Planning
73
3.5 Analyzing and defining environment requirements

This section describes what you must know before installing IBM TotalStorage Productivity Center for Data. Before you start to install the product, you should gather the required information and check prerequisites: For installations in a Windows environment, either disable or uninstall Internet Information Services (if it is already installed) from the servers on which the Agent Manager and TotalStorage Productivity Center Server software will be installed. In our environment, we uninstalled IIS. For detailed information, refer to Installing Internet Information Services (IIS) on page 145. Grant the following privileges to the Windows user account that will be used to install the TotalStorage Productivity Center: Act as part of the operating system. Create a token object. Adjust memory quotas for a process. Replace a process-level token. Log on as a service. Identify any firewalls and obtain the required authorization to pass network traffic through them. Obtain the static IP addresses to use for the TotalStorage Productivity Center servers. Are the operating systems on the servers and client at the correct level to deploy components of IBM TotalStorage Productivity Center for Data? For example, for AIX, you should 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 network connectivity. Use the following commands: For Windows: ipconfig ping
74
For UNIX and Linux: ifconfig ping
Is there a correctly setup 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 3-3. You can enter host names to see if names are resolved properly.
Figure 3-3 Result of nslookup command
Which ports are opened and ready for use? For example, in Windows, UNIX, or Linux environments, the command is netstat -an. For a sample result of this command, see Table 3-2 on page 55. 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 defaults or provide unique ones based on system requirements. Are there storage subsystems that require a vendor specific CIMOM to be installed? For example, for a Hitachi Data system, you should 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 located at: http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002841
3.5.1 Agent installation methodology

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

There are two methods to install an agent locally on a server that contains a storage subsystem.
Installation using GUI

To locally install the agent, you must have a CD media containing the IBM TotalStorage Productivity Center for Data installation program (the installer program provides a Graphical User Interface (GUI) for installation purposes). To install the agent, you must have information about: Data Manager server name and port (the default is 2078.) Agent Registration Password (the password you specified when you were installing Agent Manager) Agent listen port (the default is 9510.)
Installation using the command line

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

You can remotely install agents to: Machines in the same domain or to machines in a different domain. Windows, UNIX, and Linux machines. A target machine's local drive. The local drive represents the administrative share, such as \\computer_name\c$. You cannot install the agent to a mapped drive, because the installation will fail and the installation program will report that there are no standard shares.
76
Before you remotely install an agent, you should 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 box and a domain administrator on the foreign domain. Note: 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, meaning that it needs installation GUI access. For further information, refer to the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.
3.5.4 Interoperability namespace summary table

The interoperability namespace for a CIMOM is discoverable through SLP and is automatically populated in the TotalStorage Productivity Center GUI for CIMOMs discovered through SLP. For CIMOMs that are manually entered rather than discovered through SLP, you should check their providers documentation for the correct interop namespace. The following provider table of interop namespaces (Table 3-6) reflects the namespaces at the time this IBM Redbook was written. Important: When providers release new versions of their products, these values could change. Check the providers documentation for that provider's interop namespace.
Table 3-6 IInteroperability namespaces Vendor Cisco Brocade Interoperability namespace root/cimv2 /root/interop or /root/brocade1 Note: Contact your switch vendor for the correct namespace to use. /interop
McDATA
Chapter 3. Planning
77
Vendor
Interoperability namespace
ESS, DS6000, DS8000, and SVC Engenio EMC Hitachi
/root/ibm /interop /root/emc /root/hitachi/dm35 for HiCommand 3.5 /root/hitachi/dm42 for HiCommand 4.0 /root/hitachi/dm42 for HiCommand 4.2 /root/hitachi/dm43 for HiCommand 4.3 /root /root/sun3510 or /interop Note: This is for a subsystem and not a switch.
HP SUN StorEdge
IBM Tape ADIC Tape
/root/ibm root/cimv2
3.6 Customer support

To get support for IBM TotalStorage Productivity Center for Data V. 3.1., you can contact IBM client support in one of the following ways: Go to the Data Manager technical support Web site at: 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 should consult the Web site for client support telephone numbers. You can also review the IBM Software Support Handbook, which is available at: http://techsupport.services.ibm.com/guides/handbook.html Note: To get online support, you should register your company and yourself. When you contact client support, be prepared to provide identification information for your company so that support personnel can readily assist you. Company identification information might also be needed to access various online services available on the Web site.
78
Chapter 3. Planning
79
80
Chapter 4.
Installation
This chapter describes how to install IBM TotalStorage Productivity Center for Data V3.1. We discuss tasks that are necessary to determine whether the clients environment fulfills IBM TotalStorage Productivity Center for Data V3.1 requirements and are necessary to successfully install the product. This chapter covers the installation part of the certification exam. This chapter contains the following topics: What you should know about the installation section of exam objectives Installing TotalStorage Productivity Center Windows installation steps GUI for Web Access under Windows 2003
81
4.1 What you should know about the installation section of exam objectives
We discuss the following topics that cover the installation part of the certification exam: Given access to a server, determine if it has the correct DNS and SNMP configuration. Given a qualified DBA (Database Administrator) and supported RDBMS installed, determine if system resource access and a DB2 instance exists. Given available TCP ports, determine that they are available, so that IBM TotalStorage Productivity Center for Data V3.1 can use them. Given the IBM TotalStorage Productivity Center for Data V3.1 media, perform the installation steps using an installer method. Given a successful installation, determine if errors exist in the install logs to verify the installation. Given that the IBM TotalStorage Productivity Center for Data V3.1 is installed and validated, use the GUI to determine that appropriate services are running. Given a qualified client administrator, perform a knowledge transfer so that the administrator can support and manage IBM TotalStorage Productivity Center for Data V3.1. The instructions given in this chapter are meant to be followed to successfully install and set up an TotalStorage Productivity Center for Data environment for both Windows and AIX platforms. Installing IBM TotalStorage Productivity Center for Data consists of the following tasks: Installing the Agent Manager Installing the Data Manager Server Installing the Agent Installing the Client User Interface
4.2 Installing TotalStorage Productivity Center

The installation of TotalStorage Productivity Center has changed with V3.1 from prior releases. Each marketing package (for example, TotalStorage Productivity Center for Data as opposed to TotalStorage Productivity Center Limited Edition) contains the complete TotalStorage Productivity Center product, and all functions
82
are installed. The licenses that are shipped with each package limit the function available at the graphical user interface level. When you install TotalStorage Productivity Center V3.1, you are no longer prompted to select product components such as TotalStorage Productivity Center for Data or TotalStorage Productivity Center for Disk, which was the case in TotalStorage Productivity Center V2. The installable components available with TotalStorage Productivity Center V3.1 are: Database Schema Data server Device server Graphical User Interface (GUI) Command Line Interface (CLI) Data agent Fabric agent The CLI is considered optional. The Data agent and Fabric agents are likely to be installed in multiple locations. The GUI is installed wherever you want to control TotalStorage Productivity Center. In this chapter, we show installation mainly for a Windows 2003 environment; UNIX and Linux installation steps are the same with only one significant difference, that is, which setup file to run to start the installation.
4.2.1 Installing Agent Manager

The Agent Manager server is the computer system where the Agent Manager service and Agent Recovery service run. Put the Agent Manager server on a server-class computer system that runs one of the supported operating systems. Do not put the Agent Manager on the same computer system as an active Web server. The agent recovery service and the Web server both require port 80. A port conflict for the agent recovery service prevents the Agent Manager from starting. Registry information can only be put in a local or remote DB2 database. To estimate the size of the registry data, keep in mind the following factors: The number of agents in your environment. How long configuration data will be kept in the database. The length of rows in the agent tables. It can vary depending on the type of columns. For example, a column, which holds agent error information, can be up to 2000 characters.
Chapter 4. Installation
83
Table 4-1 can be used to estimate the size of the registry for your environment.
Table 4-1 The estimated size of a 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
4.2.2 Installing Agent Manager on Windows

Before you start the installation, check that the following steps have been done: If the Agent Manager is already installed or reinstalling because of previous installation failure, you must uninstall the Agent Manager and remove its WebSphere configuration. See the uninstall procedure. Check for port conflicts by issuing the following command:
netstat -a
The following ports should 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 different port numbers for the Agent Manager. The ports that need to be reserved are as follows: 50000 9511 9512 9513 80 DB2 port Registration port Secure port Public port HTTP server port
You should have sufficient authority, such as administrative 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. IBM TotalStorage Productivity Center provides an integrated storage infrastructure management solution that is designed to allow you to manage all of
84
your storage infrastructure, between the hosts through the network and fabric, through to the physical disks. It can help simplify and automate the management of devices, data, and storage networks. IBM TotalStorage Productivity Center V3.1 offers a simple, easy to install package with management server support added for IBM AIX 5L V5.3 and integrating IBM DB2 as the management server database. The default installation directory is: c:\Program Files\IBM\... (for Windows) /opt/IBM/...(for UNIX and Linux) You can change this path during installation setup. There are two types of installation: Typical and Custom.
4.2.3 Typical installation

The Typical installation allows you to install all of the components of the TotalStorage Productivity Center V3.1 on the local server, by selecting the options Servers, Agents, and Clients. Our recommendation is not to use the Typical installation, because you have much better control of the installation when you use the custom installation method.
4.2.4 Custom installation

The Custom installation allows you to install each component of the TotalStorage Productivity Center separately and deploy remote Fabric and Data agents on different computers. This is the installation method that we recommend.
4.2.5 CD layout and components

In this section, we describe the contents of the product CDs at the time of the writing. This is just to give you an idea of the CD content. You can install the following components from different CDs: CD1: OS: Windows, AIX, and Linux RH 3 Database Schema Data server Device server
85
GUI CLI Local Data agent Local Device agent Remote installation of Device agent CD2: OS: Windows, AIX, Linux RH 3, Linux Power, Linux s390 (Linux on a IBM System z server), Solaris, and HP-UX Local Data agent Local Device agent Remote installation of Data agent Remote installation of Device agent CD3: Data upgrade for all platforms.
4.2.6 Configuration
There are two supported environments: a one server environment and a two server environment. You must install the Data server and Device server on one computer.
One server environment

In this environment, all the components are installed on one server: DB2 Agent Manager Data server Device server CLI GUI
Two server environment

In a two server environment, you would install the components as follows. Note that you can have DB2 on a remote server. The components are: Server 1 DB2 Agent Manager Server 2 DB2
86
Data server Device server GUI CLI
For a custom installation

The user IDs and passwords you need for a custom installation are: DB2 Administrator User ID/Password or DB2 User ID/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: ~ @ # % ^ & ( ) - _ { } . WebSphere Application Server User ID/Password or Host Authentication Password must contain characters from the following categories: Uppercase characters: A through Z Lowercase characters: a through z Numeric characters: 0 through 9 Non-alphanumeric characters: - _ . Common Agent Windows Service User ID or NAS Filer User ID must contain characters from the following categories: Uppercase characters: A through Z Lowercase characters: a through z Numeric characters: 0 through 9 Non-alphanumeric characters: ` ~ # % ^ & ( ) - _ { } ' . Common Agent Windows Service Password or NAS Filer Password must contain characters from the following categories: Uppercase characters: A through Z Lowercase characters: a through z Numeric characters: 0 through 9 Non-alphanumeric characters: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < >/?
87
Common Agent Registration Password or Resource Manager Registration User ID/Password must contain characters from the following categories: Uppercase characters: A through Z Lowercase characters: a through z Numeric characters: 0 through 9 Non-alphanumeric characters: ` ~ @ # % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < >/?
User IDs and passwords created during installation

Table 4-2 through Table 4-12 on page 94 contain information about the user IDs and passwords used during the installation of the TotalStorage Productivity Center prerequisites and components.
Table 4-2 Installing DB2 and Agent Manager Item Installing DB2 and Agent Manager OS All. Description Log on Windows as a local Administrator. User ID User ID used to log on. Password Used to log on. Created when Used when Used to log on Windows to install DB2 and Agent Manager. ITSOs user ID and password Administrator/ password.
Group Administrator.
88
Table 4-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 Device server and Data server installation. Used when Used to log on Windows to install Device and Data server.
Group
Password
ITSOs user ID and password tpcadmin/ tpcadmin.
Administrator .
New user ID used to log on to Windows.
New password used to log on Windows.
89
Table 4-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, gives root authority. User ID Created when Has to be created before starting Data agent or Fabric agent installation. Used when Used to log on to Windows to install Data agent or Fabric agent.
Group
Password
ITSOs user ID and password tpcadmin/ tpcadmin.
Administrator.
New user ID used to log on to Windows.
New password used to log on to Windows.
To install a GUI or CLI, you do not need any particular authority or special user ID.
Table 4-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 below. 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
Password New password.
ITSOs user ID and password db2tpc/db2tpc.
90
DB2 user ID and password rules

DB2 user IDs and passwords must follow these rules. User IDs cannot be any of the following: UNIX user names and passwords cannot be more than eight characters long. They cannot start with a numeric digit or end with the dollar sign character $. Windows 32-bit user IDs and passwords can contain one to 20 characters. Group and instance names can contain one to 8 characters. User IDs cannot be any of the following: USERS ADMINS GUESTS PUBLIC LOCAL User IDs cannot begin with: IBM SQL SYS User IDs cannot include accented characters. UNIX users, groups, and instance names must be lowercase. Windows 32-bit users, groups, or instance names can be any case. DB2 creates a user group with the following administrative rights: Act as a part of an operating system. Create a token object. Increase quotas. Replace a process-level token. Log 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.
91
Table 4-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
We recommend you create a password.

Group User ID Password No default, if not specified, one is generated automatically. ITSOs user ID and password tpctpc.
Important: Do not change the Agent Registration password under any circumstances. Changing this password renders the certificates unusable.
Table 4-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 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
Password changeMe (default).
92
Table 4-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 for the Common Agent to run under. User ID Created when Specified when you install Data agent or Fabric agent (only local). Password ITSOs user ID and password tpcadmin/ tpcadmin. Used when
Group
Administrators
If you do not specify anything, itcauser is created by default.
Table 4-9 Host authentication password Item Host authentication password OS All. Description 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
User ID
Password Must be provided.
Table 4-10 NAS filer login user ID and password Item NAS filer login user ID and password OS Windows. Description Created when Specified when you run NAS discovery. User ID Password ITSOs user ID and password Used when
Group
93
Table 4-11 Resource manager registration user ID and password Item Resource manager registration user ID and password OS All. Description Created when Specified when you install Device server and Data server. User ID manager (default). Password password (default). Used when Used when Device server and Data server have to register to Agent Manager. ITSOs user ID and password manager/ password.
Group
Table 4-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 one. User ID If not provided, it will be created. Created when Specified when you install Device server. Password If not provided, it will be created. Used when Used when Device server has to communicate with WebSphere. ITSOs user ID and password tpcadmin/ tpcadmin.
Group
4.3 Windows installation steps

This section describes the installation of TotalStorage Productivity Center in a Windows environment.
4.3.1 DB2 install for Windows

In this section, we show a typical installation of DB2 8.2. Before beginning the installation, it is important that you log on to your system as a local administrator with Administrator authority for Windows or root authority for UNIX and Linux (see Table 4-2 on page 88).
94
Important: If you update DB2 from an older version, for example, from DB2 7.2 to DB2 8.2, the TotalStorage Productivity Center installer might not recognize the DB2 version. The workaround follows: Execute the following command in a DB2 environment (on Windows 2003, you can use db2cmd):
db2 update dbm cfg using JDK_PATH <DB2_InstallLocation>\java\jdk db2 update dbm cfg using JDK_PATH "C:\PROGRAM Files\IBM\SQLLIB\java\jdk"
Restart TPC V3.1 installer. 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.
95
2. If Windows autorun is enabled, the installation program should start 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 4-1. Select Install Product to proceed with the installation.
Figure 4-1 DB2 Setup welcome
3. The next window allows you to select the DB2 product to be installed. Click Next to proceed, as shown in Figure 4-2 on page 97.
96
Figure 4-2 Select product
The InstallShield Wizard starts (see Figure 4-3).
Figure 4-3 Preparing to install
97
4. The DB2 Setup wizard window is displayed, as shown in Figure 4-4. Click Next to proceed.
Figure 4-4 Setup wizard
5. You have to read and click I accept the terms in the license agreement (see Figure 4-5 on page 99).
98
Figure 4-5 License agreement
6. To select the installation type, accept the default of Typical and click Next to continue (see Figure 4-6).
Figure 4-6 Typical installation
99
7. Accept the defaults and proceed with Install DB2 Enterprise Server Edition on this computer (see Figure 4-7). Click Next to continue.
Figure 4-7 Installation action
8. The window shown in Figure 4-8 on page 101 shows defaults for the drive and directory to be used as the installation folder. You can change those or accept the defaults and click Next to continue.
100
Figure 4-8 Installation folder
9. Set the user information for the DB2 Administration Server; choose the domain of this user. If it is a local user, leave the field blank.
101
10.Type a user name and password of the DB2 user account that you want to create (Figure 4-9). You can refer to Table 4-5 on page 90. DB2 creates a user with the following administrative rights: Act as a part of an operating system. Create a token object. Increase quotas. Replace a process-level token. Log on as a service.
Figure 4-9 User Information
11.Accept the defaults in the window shown in Figure 4-10 on page 103, and click Next to continue.
102
Figure 4-10 Administration contact list
12.Click OK when the warning window shown in Figure 4-11 opens.
Figure 4-11 Warning
103
13.In the Configure DB2 instances window, accept the default and click Next to continue (see Figure 4-12).
Figure 4-12 Configure DB2 instances
104
14.Accept the defaults, as shown in Figure 4-13. Verify that the radio button next to Do not prepare the DB2 tools catalog on this computer is checked. Click Next to continue.
Figure 4-13 Prepare DB2 tools catalog
105
15.In the window shown in Figure 4-14, click Defer the task until after installation is complete and then click Next to continue.
Figure 4-14 Health monitor
106
16.The window shown in Figure 4-15 is presented. Click Install to continue.
Figure 4-15 Start copying files
107
The DB2 installation proceeds and you see a progress window similar to the one shown in Figure 4-16.
Figure 4-16 Installing DB2 Enterprise Server Edition installation progress
17.When the installation completes, click Finish, as shown in Figure 4-17 on page 109.
108
Figure 4-17 DB2 Setup wizard
18.If you get the DB2 product updates window shown in Figure 4-18, click No, because you have already verified that your DB2 version is at the latest recommended and supported level for TotalStorage Productivity Center, as mentioned in Database support on page 33.
Figure 4-18 DB2 Product Updates window
109
19.Click Exit First Steps (see Figure 4-19) to complete the installation.
Figure 4-19 Universal Database First Steps window
Verifying the installation

1. To verify the DB2 installation, check if the db2tpc user has been created and included in the DB2ADMINS group. 2. Open a Command Prompt window and enter the db2level command to check the version installed, as shown in Figure 4-20 on page 111.
110
Figure 4-20 db2 clplevel 20
Figure 4-21 shows the DB2 window services created at the end of the installation.
Figure 4-21 Windows services showing DB2 services
111
4.3.2 Agent Manager install

This is a typical installation of Agent Manager 1.2.2. When you install the Agent Manager, you are also installing the Embedded version of IBM WebSphere Application Server - Express V5.0 (WebSphere Express), without the Administrative console to manage WebSphere itself. To start the Agent Manager installer, run the following program from the EmbeddedInstaller directory: setupwin32.exe (for Windows) If this fails due to a Java error, try setupwin32.exe -is:javahome ..\jre\windows. setupAix.bin (for AIX) If this fails due to a Java error, try setupAix.bin -is:javahome ../. setupLinux.bin (for Linux x86) If this fails due to a Java error, try setupLinux.bin -is:javahome ../. setupLinuxPPC.bin (for Linux on Power PC) If this fails due to a Java error, try setupLinux.bin -is:javahome ../. setupSolaris.bin (for Solaris) If this fails due to a Java error, try setupLinux.bin -is:javahome ../. Important: Log on with a user ID that has administrative authority on Windows and root authority on UNIX or Linux. The Installation Wizard starts, and you see a window similar to the one in Figure 4-22.
Figure 4-22 Install wizard window
112
1. Select a language and click OK (see Figure 4-23).
Figure 4-23 Language selection window
1. Read and accept the terms of the license agreement, and select I accept the terms of the license agreement. Click Next to continue (see Figure 4-24).
Figure 4-24 License window
113
2. Figure 4-25 shows the Directory Name for the installation. Click Next to accept the default or click Browse to install to a different directory.
Figure 4-25 Installer directory name
3. The Agent Manager Registry information window is displayed, as shown in Figure 4-26 on page 115. On this window, specify the type of database, Database Name, or Directory and type of Database Connection. 4. You can accept the defaults and click Next to continue.
114
Figure 4-26 Wizard installing the Agent Manager
5. In the next window shown in Figure 4-27 on page 116, enter the following database information: Database Software Directory Enter the directory where DB2 is installed. The default directory is: C:\Program Files\IBM\SQLLIB (for Windows) /opt/IBM/SQLLIB (for UNIX or Linux)
Database user name Database Password Host name of the Database Server Database Port This is required for a remote database. After entering the information, click Next to continue.
115
Figure 4-27 Agent Manager database information
6. Figure 4-28 on page 117 shows a window where you have to enter the following information: Host Name Alias or Fully Qualified Host Name If you specify an IP address, you will get the warning window shown in Figure 4-29 on page 118. Application Server Name for Agent Manager Accept the default name or enter a different name. Registration Port The default port is 9511 for the server-side SSL. Secure Port The default port is 9512 for client authentication, 2-way SSL. Public Port and Secondary Port for the Agent Recovery Service The public communication port default is 9513. Other options You also have these options: Do not use port 80 for the Agent Recovery service. Start the agent manager after the installation is complete. Autostart the Agent Manager each time the system restarts.
116
We recommend that you select all of these options, except for Do not use port 80 for the Agent Recovery service. To check for other applications, which are using port 80, run the following command: netstat -an Look for port 80 in the listening state. If there is an application using port 80, stop that application, and then continue with the installation of Agent Manager. Note: If you want Agent Recovery Service to run, you must stop any service using port 80. Agent Recovery Service will install any service that is using port 80, but will not start.
Figure 4-28 Wizard host name without port designation
117
7. If you specify an IP address instead of a fully qualified host name for the WebSphere Application Server in the window in Figure 4-28 on page 117, you will be presented the window shown in Figure 4-29. We recommend you click Back and specify a fully qualified host name.
Figure 4-29 Warning about the specified IP window
118
8. The next window is the Security Certificates window (see Figure 4-30). We highly recommend that you accept the defaults to generate new certificates for a secure environment. Click Next to continue.
Figure 4-30 Create security certificates
119
In the next window shown in Figure 4-31, you specify the Security Certificate settings. 9. To create Certificates, you have to specify a Certificate authority password. You need to specify this password in order to look at the certificate files once they are generated. Make sure you record this password. 10.The second password specified in this window is the Agent Registration password. The default Agent Registration password is changeMe. We recommend you specify a unique password and record it. 11.After entering the passwords, click Next to continue.
Figure 4-31 Security certificate password window
120
12.The User input summary window is displayed (see Figure 4-32). If you want to change any settings, click Back and return to the window where you set the value. If you do not need to make any changes, click Next to continue.
Figure 4-32 User input summary window
121
13.Review the summary information window (see Figure 4-33) and click Next to continue.
Figure 4-33 Summary information window
14.The Agent Manager installation starts and you see several messages, such as those in Figure 4-34 on page 123 and Figure 4-35 on page 123.
122
Figure 4-34 Installation progress window
15.Next you see the Database IBMCDB creation status window.
Figure 4-35 Registry database window
123
16.The Summary of Installation and Configuration Results window is displayed (see Figure 4-36). Verify if the Agent Manager has successfully installed all of its components. Review the window and click Next to continue.
Figure 4-36 Summary of Agent Manager configuration options window
124
17.The last window (Figure 4-37) shows that the Agent Manager has been successfully installed. Click Finish to complete the Agent Manager installation.
Figure 4-37 Finish the Agent Manager installation
Verifying the installation

You can verify the installation by running the healthcheck utility from a command-prompt. Go to the directory: <InstallDir>\Program Files\IBM\AgentManager\toolkit\bin and run healthcheck. Verify that the ARS.version field shows the level you have installed (in our installation, it is 1.2.2.2), and, that, at the end, you get the message Health Check passed, as shown in Figure 4-38 on page 126.
125
Figure 4-38 Healthcheck utility
After the completion of the Agent Manager installation, you can verify the connection to the database (see Figure 4-39 on page 127). From a Command Prompt, enter db2cmd db2 connect to IBMCDB user db2tpc using db2tpc.
126
Figure 4-39 DB2 command line CONNECT
4.3.3 Install TotalStorage Productivity Center components

Now that the prerequisites have been installed, we install the TotalStorage Productivity Center components. Before starting the install, verify that DB2 8.2 Enterprise Edition Fix Pack 7a has been installed and has been started. Important: Log on to your system as a local administrator with database authority for Windows. The user ID must have root authority for UNIX or Linux. 1. For Windows, if Windows autorun is enabled, the installation program should start automatically. If it does not, open Windows Explorer and go to the TotalStorage Productivity Center CDROM drive or directory. Double-click setup.exe. 2. Chose your language and click OK (see Figure 4-40).
Figure 4-40 Language selection window
127
3. The License Agreement window is displayed. Read the terms and select I accept the terms of the license agreement. Then click Next to continue (see Figure 4-41).
Figure 4-41 License window
Figure 4-42 on page 129 shows how to select Typical or Custom installation. You have the following options: Typical installation Allows you to install all of the components on the same computer by selecting Servers, Agents, and Clients. Custom installation Allows you to install each component separately. Installation licenses This 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 TotalStorage Productivity Center for Data package, the license will be automatically installed 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 allows you to install the license key from the CD. You do not have to install the IBM TotalStorage Productivity Center for Fabric product.
128
In this chapter, we document Custom installation. Click the radio button to the left of Custom installation, and then click Next to continue.
Figure 4-42 Custom installation
129
In the Custom installation, you can select all the components in the window shown in Figure 4-43. This is the recommended installation scenario. In our scenario, we show the installation in stages. 1. As the first step, we select the option to Create database schema, and click Next to proceed (see Figure 4-43).
Figure 4-43 Custom installation component selection
2. To start the Database creation, you have to specify a DB2 Database administrator user ID. We suggest that you use the same DB2 user ID you have created before. Then click Next, as shown in Figure 4-44 on page 131.
130
Figure 4-44 DB2 user ID and password
3. In the next window, you have to enter your DB2 user ID and Password again (see Table 4-5 on page 90). Do not take the default of Use Local Database. Click the radio button next to Create local database. By default, a database is created named TPCDB. Click Next to continue (see Figure 4-45).
Figure 4-45 DB2 user and create local database
131
4. The next window allows you to change the default space assigned to the database. At this time, you do not need to change these values and you can accept defaults. You have to specify the Schema name. In our installation, we chose TPC. For better performance, we recommend that you: Allocate TEMP DB on a different physical disk than the TotalStorage Productivity Center components. Create larger Key and Big Databases. 5. Select System managed (SMS) and click OK to proceed (see Figure 4-46).
Figure 4-46 DB schema space
6. The next window is the Database schema installation progress window (see Figure 4-47 on page 133). Wait for the installation to complete.
132
Figure 4-47 Installing DBSchema wait message
7. Upon completion, the successfully installed window is displayed. Click Finish to continue (see Figure 4-48).
Figure 4-48 Installation summary information
133
Verifying installation
To check the installation result, start DB2 Control Center, verifying that you have two DB2 instances in your environment, as shown in Figure 4-49.
Figure 4-49 Verifying DB2 installation
Important: Do not edit or modify anything in DB2 Control Center. This can cause serious damage to your tablespace. Simply use this to browse your configuration.
Log files
Check for errors and Java exceptions in the log files at the following locations: Install<time stamp>.log file from system temp directory or <InstallLocation>. <InstallLocation>\dbschema\log Look for dbschema.out, dbschema.err, and DBSchema.log. <InstallLocation>\log. <InstallLocation>\TPC.log. Check for a success message at the end of INSTALL<time stamp>.log file for a successful installation.
134
4.3.4 Installing Data server, Device server, GUI, and CLI

In our environment, we did a custom installation of Data server, Device server, GUI, and CLI.
Pre-installation tasks
To install the Data server or Device server component, you must log on Windows 2003 with a User 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. We recommend you create a user ID for installation. We created the user ID TPCADMIN (refer to Table 4-3 on page 89). 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. The Data server must be successfully installed prior to installing the GUI. The Device server must be successfully installed prior to installing the CLI.
135
Custom installation
1. Start the TotalStorage Productivity Center installer. 2. Select the components you want to install. In our scenario, we select the four Server components, as shown in Figure 4-50. Tip: We recommend that you install the Data agent and the Device agent in a separate step. If you install all of the components at the same time, if one fails for any reason (for example, space or passwords), the installation suspends and a rollback occurs, uninstalling all of the previously installed components.
Figure 4-50 Select components to install
3. Specify the DB2 user ID defined previously (see Table 4-5 on page 90) and click Next, as shown in Figure 4-51 on page 137.
136
Figure 4-51 User ID and password
4. Check the DB2 user ID and click the radio button next to the option Use local database. Click Next to continue (Figure 4-52).
Figure 4-52 Use local database selection
137
5. The window in Figure 4-53 on page 139 allows you to 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 to the existing Administrators group. 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 4-9 on page 93. WebSphere Application Server admin ID and Password You can use the TPC Superuser here. In our case, we used TPCADMIN. See Table 4-12 on page 94 for further details. Click Next to continue.
138
Figure 4-53 Component information for installation
The next window, shown in Figure 4-54 on page 140, shows the Agent Manager information. 6. You have to specify: Host name or IP address The fully qualified name or IP address of the Agent Manager server. Port (Secured) Port number of the Agent Manager server. If acceptable (not in use by any other application), use the default port 9511. Port (Public) The public communication port. If acceptable (not in use by any other application), use the default of 9513. User ID This is the user ID used to register the Data server or Device server with the Agent Manager. The default is manager. You previously specified this user ID during the Agent Manager installation (see Figure 4-31 on page 120). Password This is the password used to register the Data server or Device server with the Agent Manager. The default is password.You previously specified this user ID during the Agent Manager installation (see Figure 4-31 on page 120).
139
Password: Common agent registration password This is the password used by the common agent to register with the agent manager. This was specified when you installed the Agent Manager. The default is changeMe. See Table 4-7 on page 92 for further details. Click Next to continue.
Figure 4-54 Agent Manager information
7. The Summary information window is displayed. Review the information and click Install to continue (see Figure 4-55 on page 141).
140
Figure 4-55 Summary of installation
The installation starts. You might see several messages related to Data Server installation similar to Figure 4-56.
Figure 4-56 Installing Data Server
141
Then, you might see several messages about the Device server installation, as shown in Figure 4-57.
Figure 4-57 Installing Device Server
8. After the GUI and CLI installation messages, you see the summary information window (see Figure 4-58). Read and verify the information, and click Finish to complete.
Figure 4-58 Component installation completion window
142
Verifying installation
At the end of the installation, the Windows Services shows that the Data server and Device server services (shown in Figure 4-59) have been installed.
Figure 4-59 Windows service
You should check that the Administrators group contains the newly created TPC user ID. The user ID TSRMsrv1 is created by default by the installation program.
Log files for Data server

Check the logs for any errors or Java exceptions: Install<time stamp>.log file from system temp directory or <InstallLocation>. <InstallLocation>\data\log look for dataserver.out, dataserver.err, or DataServer.log <InstallLocation>\log From <InstallLocation>\data\log: Cimom_000001.log createdLuns.log guidinstallog.txt Scheduler_000001.log Server_000001.log TPCD_000001.log TSRMsrv1.out
143
INSTALL<time stamp>.log file should not have any exceptions and it should show install successful at the bottom. The Server_000001.out file mentions that the server is ready to accept connections.
Log files for Device server

These are the log files for the Device server: <InstallLocation>\device\apps\was\logs <InstallLocation>\TPC.log <InstallLocation>\device.log <InstallLocation>\device\Mgrlog.txt If successful, you see the Server server1 open for e-business message in <InstallationLocation>\device\apps\was\logs\server1\SystemOut.log. In case of failure, you can find errors and exceptions here.
Log files for GUI

These are the log files for GUI: Install<time stamp>.log file from the system temp directory or <InstallLocation>. <InstallLocation>\gui\log Look for gui.out, gui.err, or GUI.log Check the log files for any errors.
Log files for CLI

These are the log files for CLI: <InstallLocation> <InstallLocation>\cli\log <InstallLocation>\cli\log Check the log files for any errors.
4.4 GUI for Web Access under Windows 2003

You can configure the TotalStorage Productivity Center V3.1 user interface to be accessible from a Web browser. Once this is done, a user can access the TotalStorage Productivity Center GUI by entering the URL, and the TotalStorage Productivity Center GUI applet will be downloaded into the browser and executed. It looks and acts exactly as though it is on the native server. You can
144
install the interface on any of the TotalStorage Productivity Center servers, management consoles, or workstations.
4.4.1 Installing Internet Information Services (IIS)

In order to configure the Web server on the TotalStorage Productivity Center Server, make sure that IIS is installed. It is not installed by default, but it is a part of Windows Server 2003. To install it, follow these directions: 1. On the Windows Taskbar, select Start Control Panel Add or Remove programs. 2. Select Add/Remove Windows Components from the task bar on the left (see Figure 4-60).
Figure 4-60 Add/Remove Windows Components icon
3. Highlight the entry for Application Server. Click the Details button to continue (see Figure 4-61).
Figure 4-61 Windows Components window
145
4. Check the box labeled Internet Information Services (IIS). Then click OK to continue (see Figure 4-62).
Figure 4-62 Installing IIS
5. You are taken back to the window in Figure 4-61 on page 145. Click Next to install IIS. An Installation Progress window shows your progress. You need to have your Windows Server 2003 CD-ROM available or have a 2003 I386 directory installed on a hard disk (see Figure 4-63). If you have Service Pack 1 installed, you also need to have the Service Pack 1 CD-ROM or SP1 I386 directory available as well.
Figure 4-63 Service Pack media request
6. Once the installation has completed successfully, click Finish to complete the Windows Component Wizard (see Figure 4-64 on page 147).
146
Figure 4-64 Installation complete window
7. Cancel the Add or Remove Programs dialog. You now have IIS installed.
147
4.4.2 Configuring IIS for the TotalStorage Productivity Center GUI

You can now configure IIS to serve up the TotalStorage Productivity Center User interface. Follow these steps: 1. Open the IIS Configuration Panel by selecting Start All Programs Administrative Tools Internet Information Services (IIS) Manager (see Figure 4-65).
Figure 4-65 Open the IIS configuration window
2. Once the Internet Information Services (IIS) Manager appears, and open the Explorer window to display the Web Site Default Web Site. Right-click Default Web Site name, and click Properties from the context menu (see Figure 4-66 on page 149).
148
Figure 4-66 IIS Default Web Site Properties
The Default Web Site Properties window opens. There are three tabs that you need to configure: a. Web Site tab
149
Important: On the Web Site tab (see Figure 4-67), you can change the Description to TPC V3.1 GUI. Also, if Agent Manager is configured to use port 80 for the Agent Recovery service, you will need to change the default port to something other than 80. Port 8080 is a good alternative.
Figure 4-67 Default Web Site Properties - Web Site tab
150
b. Home Directory tab On the Home Directory tab (see Figure 4-68), change the Local Path to the GUI directory for TotalStorage Productivity Center. The default is C:\Program Files\IBM\TPC\gui.
Figure 4-68 Default Web Site Properties - Home Directory tab
151
c. Documents tab On the Documents tab (see Figure 4-69), click Add, and add TPCD.html to the list. Highlight the new name in the list, and click Move Up to move TPCD.html to the top of the list.
Figure 4-69 Default Web Site Properties - Documents tab
Click OK to save these changes. Close the IIS Manager by clicking the X in the upper right corner of the window.
4.4.3 Launch the TotalStorage Productivity Center GUI

Start your Web browser (Internet Explorer), and enter the URL you have just created. If you changed the port, you have to incorporate the port into the URL also. The format of the URL is: http://<host name>:port#
152
For example, if your host name for the TotalStorage Productivity Center server is fred.mycompany.com, and you changed the port to 8080, the URL is http://fred.mycompany.com:8080. If you left the port set to 80, the URL is: http://fred.mycompany.com If you start the Web browser on your TotalStorage Productivity Center server machine, you can use localhost rather than the network name: http://localhost The IBM TotalStorage Productivity Center for Data window is displayed (see Figure 4-70). This is the anchor page for the TotalStorage Productivity Center GUI Java applet, and must remain open as long as the TotalStorage Productivity Center GUI is running.
Figure 4-70 TotalStorage Productivity Center for Data window
153
A security certificate approval window will be displayed (see Figure 4-71). Depending on network transmission rates, it could take a few minutes for the window to appear. Click Yes to accept the certificate. If you click No, the TotalStorage Productivity Center GUI does not load, and you have to relaunch the TotalStorage Productivity Center GUI URL to restart.
Figure 4-71 Security certificate
At this point, the Java applet for the TotalStorage Productivity Center GUI will download. The applet jarfile is 15.6 MB and can take some time to load into your browser the first time. Be patient because there is no progress bar displayed to indicate what progress is being made. Once 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 should load much faster. Once the applet has loaded, it launches the TotalStorage Productivity Center GUI. In the center of the GUI, the Sign On window appears. It should be prefilled with the Server address and access port (9549 for TotalStorage Productivity Center V3.1). Enter your TotalStorage Productivity Center Server User ID and password, and click OK to continue (see Figure 4-72 on page 155).
154
Figure 4-72 IBM TotalStorage Productivity Center Sign on window
The TotalStorage Productivity Center GUI will be displayed (see Figure 4-73) and will have all the functionality of the native GUI on the TotalStorage Productivity Center Server.
Figure 4-73 TotalStorage Productivity Center V3.1 GUI
155
156
Chapter 5.
Configuration
In this chapter, we cover configuration concepts for deploying IBM TotalStorage Productivity Center for Data V3.1. TotalStorage Productivity Center for Data is a powerful console for the storage environment that provides a set of policy-driven automated tools for managing storage capacity, availability, events, performance, and assets in your enterprise environment. Data Manager can help you identify, evaluate, control, and predict your enterprise storage management assets. Because it is policy-based, it can detect potential problems and automatically make adjustments based on policies and actions you have established. This chapter provides a guideline for you to configure the TotalStorage Productivity Center for Data for your environment and obtain several different reports for your environment. This chapter contains the following sections: Agent deployment options Local installation of Data and Fabric Agents Verifying the installation Upgrading the Data Agent Alert disposition (SNMP and mail) Log file retention
157
Scan/probe agent administration History aggregator Data Manager CIMOM logins Data Manager resource history retention Configuring chargeback
158
5.1 Agent deployment options

TotalStorage Productivity Center for Data receives almost all of the information it provides in its reports and repositories solely through the Data Agents on the managed servers and computers. It also relies on the presence of a Data Agent infrastructure to perform policy driven management. Although TotalStorage Productivity Center for Data can also receive some information directly from the storage subsystems through CIM agents without the presence of any Data Agents, we recommend this only for very special requirements because this limits the overall product capabilities to a large extent. There are two ways of deploying the Tivoli Common Agent and the TotalStorage Productivity Center Data Agent. You can choose between local installation and remote installation. In this guide, we will only cover the local installation. Local installation means that you have to be logged on to the computer on which you want to install the agent code. The TotalStorage Productivity Center Installer checks if there is a Tivoli Common Agent already installed and if not, installs this component. The local installation process is provided either interactively using a graphical user interface or unattended (silent) mode. This is useful in cases where you have to script the installation or where you simply do not have access to the GUI of the system (for example, telnet access only). Local agent installation might be practical for a limited number of computers but becomes rather elaborate and time-consuming as the number of managed computers grows.
5.2 Local installation of Data and Fabric Agents

Before you can start to install the Data Agent, you have to verify that the TotalStorage Productivity Center Server and the Tivoli Agent Manager are installed, running, and can both be reached over the network. For a successful installation, you have to provide information, which is summarized below: The host name or the IP Address of the Data server The port to communicate with the Data server The host name or the IP Address of the Device server The port to communicate with the Device server The host authentication password The host name or the IP Address of the Tivoli Agent Manager Server
Chapter 5. Configuration
159
The ports to communicate with the Tivoli Agent Manager Server The Common Agent registration password
5.2.1 Interactive installation

Start the TotalStorage Productivity Center Installer by running setup.exe on Windows systems and setup.sh on UNIX and Linux systems. You find these programs in the root directory of the installation CD. In the following window images, we show the dialog of an installation on a Windows platform. Data Agent and Fabric Agent are both installed at the same time. Of course, you can install either the Data Agent or the Fabric Agent separately. 1. In the first window, select the preferred language for the installer, as shown in Figure 5-1.
Figure 5-1 Local interactive installation, language selection
2. Click OK. 3. The International Program License Agreement is shown (see Figure 5-2 on page 161). Read the terms and select I accept the terms of the license agreement.
160
Figure 5-2 Local interactive installation, License agreement
4. Click Next to continue.
161
5. In Figure 5-3, you can choose the type of installation. We recommend you always use Custom installation when you install the agents. So, select Custom installation by clicking the radio button next to it. In the window, you can also choose the installation path of the agents. The default is C:\Program Files\IBM\TPC under Windows and /opt/IBM/TPC under UNIX and Linux. In our example, we keep the defaults. Note that the installer not only installs files in the location that you specify in this window. There are also files installed to the C:\Program Files\Tivoli\ep Directory under Windows and the /usr/Tivoli/ep Directory under Linux and UNIX. Make sure that the installation location you specify in this window is empty. Otherwise, the installer fails.
Figure 5-3 Local interactive installation, Type of installation, installation location
6. Click Next to continue. 7. In the window in Figure 5-4 on page 163, you have to select which components of TotalStorage Productivity Center you want to install. Deselect anything but Data Agent.
162
Figure 5-4 Local interactive installation, component selection
8. Click Next to continue. 9. In the next window shown in Figure 5-5 on page 164, you have to enter the following information: Data Server Name: This is the fully qualified host name or the IP address of the machine on which the TotalStorage Productivity Center Data server and Device server is running. In our environment, the TotalStorage Productivity Center Server is on gallium.almaden.ibm.com. Data Server Port: The port that the Data Agent uses to communicate with the Data server. It is set when installing the Data server. We recommend to keep the default, which is 9549. Device Server Name: This is the fully qualified host name or the IP address of the Device server. In TotalStorage Productivity Center V3.1, it has to match the Data Server Name. In our environment, the name of the Data server and Device server is gallium.almaden.ibm.com. Device Server Port: The port that the Fabric Agent uses to communicate with the Device server. It is set when installing the Device server. We recommend to keep the default, which is 9550. Host authentication password: This is the password used by the Fabric Agent to communicate with the Device server. You specify this password when you install the Device server.
163
10.Next, you have to select some options for the Data Agent, as shown in Figure 5-5.
Figure 5-5 Local interactive installation, server, and agent settings
11.Click Data Agent Options. 12.The window in Figure 5-6 on page 165 is displayed where you can select two options: Agent should perform a scan when first installed Uncheck 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 you accept this default, so that you make sure your Data server gets a solid information base about your computer right after installation. Agent may run scripts sent by server Uncheck this option if you do not want the Data Agent to be able to run scripts, which the Data server sends. This option is checked by default. The advantage of checking this option is that you can store scripts in the server's \scripts directory, and you do not have to keep a copy of the script on every agent computer. When a script needs to be run on a particular agent, the server accesses the script from its local \scripts directory and sends it to the appropriate agent. If the Agent may run scripts sent by server option is unchecked, you must make sure that the script is stored in every agent's \scripts directory.
164
Tip: If a script with the same name exists on both the server and the agent, the script stored on the agent takes precedence. This is useful if you want to run a special version of a script on one of your agents, while running a different version of the same script across all the other agents in your environment.
Figure 5-6 Local interactive installation: Data Agent setting
13.Click OK to continue. This brings you back to the window shown in Figure 5-5 on page 164 where you have to click Next. 14.In the next window shown in Figure 5-7 on page 166, 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 that the agents use to communicate with the Tivoli Agent Manager. They are specified during the installation of the Agent Manager. We recommend keeping the default ports, which are 9511 (secure) and 9513 (public). Finally, you have to enter the Common Agent Registration password. This 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.
165
Note: If you do not specify the correct Agent Manager password, you are not allowed to continue the installation. You receive an error window and cannot continue until the correct password is entered.
Figure 5-7 Local interactive installation: Tivoli Agent Manager information
15.Click Next to continue. The Common Agent selection window is displayed (see Figure 5-8 on page 167). If a Tivoli Common Agent is already running (for example, when you install a Fabric Agent and a Data Agent is already installed or vice versa), 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 have to select to install it 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.
166
Figure 5-8 Local interactive installation: Common Agent options
16.If you click Window Service Info on the above window, you get the Common Agent Service Information window (see Figure 5-9). This information is optional. You can enter a Common Agent service name, user ID, and password that the Installer uses to create a Windows service for the Common Agent. Otherwise, by default, itcauser is created.
Figure 5-9 Common Agent services name and user information
167
17.Enter the information and click OK. This will bring you back to the window shown in Figure 5-8 on page 167 where you will have to click Next. 18.The Summary Information window is displayed (see Figure 5-10) where you can review some of the information you have entered during the installation dialog.
Figure 5-10 Local interactive installation: summary information window
19.Click Install to continue. The installer begins to install the Data Agent (Figure 5-11 on page 169).
168
Figure 5-11 Local interactive installation, installing the Data Agent
Although you could Cancel the installation while the progress bars are displayed, we strongly recommend that you do not do this. An inconsistent state of your system might be the result. Finally, a window will be displayed announcing that the installation has finished successfully, as shown in Figure 5-12.
Figure 5-12 Local interactive installation: installation complete
20.Click Finish to exit the installer.
169
5.3 Verifying the installation

After installing the server agents, you should check if the agents have registered successfully with the TotalStorage Productivity Center Server. They should do this without any further discovery. To check the communication between the TotalStorage Productivity Center Server and the agents, start the TotalStorage Productivity Center graphical user interface and log on. In the Navigation Tree shown in Figure 5-13, select Administrative Services Agents Data. You should see an entry for each of the newly installed agents. You now can right-click the entries and check if the TotalStorage Productivity Center Server can reach the agent and if the agent is up and running. In addition to that, the same context menu provides a look at the log files and the capability to set up a trace for each agent.
Figure 5-13 Verify agent installation
170
The install process creates a directory structure on the servers, which should look similar to the one shown in Figure 5-14 for a Windows server. For UNIX and Linux systems, the tree is created under /opt/IBM/ by default and otherwise looks the same.
Figure 5-14 Directory tree for Data and Fabric Agent installation
Note: The Remote Installer, however, creates a different tree structure by default. It installs the Data Agent and the Common Agent to the following directory: C:\Program\Tivoli\ep on Windows and /usr/tivoli/ep on UNIX and Linux.
171
Under Windows, you should see one service, which is called IBM Tivoli Common Agent (see Figure 5-15).
Figure 5-15 Windows Services after agent installation
The Data Agent and Fabric Agent do not show up as a service. They run under the context of the Common Agent. Under UNIX and Linux, you should see two processes. One is the nonstop process, which launches the Common Agent process, and the other one is the Common Agent itself. The output of a ps -ef command should show the results in Figure 5-16 on page 173.
172
Figure 5-16 UNIX and Linux process status after agent installation
5.3.1 Log files

The agent installation process creates a number of logs that can be checked to retrace the installation process and also to monitor the activity during normal operation. These logs provide ample detailed information and are especially useful in the case of a failed installation in order to determine the reason for the failure and to troubleshoot the installation. They are spread over several locations. Note: The default <InstallLocation> differs in local and remote administration.
Data Agent logs

The following installation logs are for the Data Agent when installed locally: <InstallLocation>\log\subagents\TPC\Data\install\ for Windows <InstallLocation>/log/subagents/TPC/Data/install/ for UNIX AND Linux
173
The following installation logs are for the Data Agent when installed remotely for Windows. <InstallLocation>\logs\ <InstallLocation>\logs\install\ <InstallLocation>\subagents\TPC\Data\log\ The following installation logs are for the Data Agent when installed remotely for UNIX and Linux: <InstallLocation>/logs/ <InstallLocation>/subagents/TPC/Data/log/ <InstallLocation>/logs/ The following operational log is for the Data Agent when installed locally for Windows: <InstallLocation>\ca\subagents\TPC\Data\log\<host name>\ The following operational log is for the Data Agent when installed locally for UNIX and Linux: <InstallLocation>/ca/subagents/TPC/Data/log/<host name>/ 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>
Common Agent logs

The following installation and operational logs are for the Common Agent when installed locally for Windows: <InstallLocation>\ca\logs\ <InstallLocation>\ca\logs\install\
174
The following installation and operational logs are for the Common Agent when installed locally for UNIX and Linux: <InstallLocation>/ca/logs/ <InstallLocation>/ca/logs/install/ The following installation and operational logs are for the Common Agent when installed remotely for Windows: <InstallLocation>\logs\ <InstallLocation>\logs\install\ The following installation and operational logs are for the Common Agent when installed remotely for UNIX and Linux: <InstallLocation>/logs/ <InstallLocation>/logs/install/
5.4 Upgrading the Data Agent

The TotalStorage Productivity Center graphical user interface allows you to upgrade your Data Agent infrastructure from a central point of management. This central upgrade is only supported for the Data Agent and the Common Agent. The Fabric Agent cannot be upgraded this way. Before you can upgrade your Data Agents from your central TotalStorage Productivity Center GUI, you have to copy the upgrade.zip files of the new Data Agent version for the operating systems, you want to perform an upgrade to the C:\Program File\IBM\TPC\data\upgrade (for Windows) and /opt/IBM/TPC/data/upgrade (for Linux and UNIX) path of your TotalStorage Productivity Center Server installation. Note that if you do not copy the upgrade.zip file, your agents may become dysfunctional.
175
The tree structure should look similar to the figure in Figure 5-17.
Figure 5-17 Copy the upgrade.zip file to the server upgrade directories
176
1. After having copied the files you need 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 5-18.
Figure 5-18 Data Agent upgrade, create an upgrade job
177
2. You then see a window similar to Figure 5-19 where you can select the computers for which you want to perform a Data Agent upgrade.
Figure 5-19 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 that have Data Agents installed. 4. Verify that the Enable check box in the top right corner of the window is ticked. 5. In the When to Run tab, you can specify if the upgrade should run immediately or should be scheduled at a later time. The Options tab offers you options for the upgrade of the Data Agents. You can specify if the Data Agent should 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 tabs, select File Save. You have to specify a name for the job. The upgrade job is now saved and runs either immediately or at the time you chose in the When to Run tab. 7. To check if the upgrades have completed successfully, right-click Data Agent Upgrades and select Refresh. You now see an entry for the upgrade job you
178
submitted. Click the 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 entry and you see the log for the job on the right pane, as shown in Figure 5-20.
Figure 5-20 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.
5.5 Alert disposition (SNMP and mail)

Alerts can be redirected to event receivers in your environment. You can configure SNMP, TEC, and e-mail receivers. 1. Select Administrative Services Configuration Alert Disposition (see Figure 5-21 on page 181).
179
2. Enter the necessary fields that are available for your environment. Your event receivers should be configured beforehand: a. For SNMP sections, it is possible to define two SNMP receivers. You have to enter the community name and host name. TotalStorage Productivity Center for Data uses the default port 162 if it is left blank. b. For the TEC receiver, define the TEC server name. TotalStorage Productivity Center for Data uses the default port 5529 if it is left blank. c. For the e-mail receiver, the following parameters are available: Mail Server: Name of the mail server in your environment. Mail Port: Port number for outgoing SMTP server. The default is 25. Default Domain: Default domain to use for sending e-mail. Return To: The e-mail address for undeliverable alerts. Reply To: The e-mail address if the user replies to an e-mail triggered by an alert. Data Administrator: The e-mail address for the notification of fatal server errors.
d. For alert log disposition, specify the number of days that you want Productivity Center for Data to keep alert records.
180
Figure 5-21 Configuring the alert log
3. Save to make the changes permanent.
5.6 Log file retention

You can define how many runs or how long you retain logs in the Data Manager repository (see Figure 5-22 on page 182). 1. Select Administrative Services Configuration Log-file retention. 2. Define the following two parameters: Maximum number of runs to keep of each schedule: Enter the number of runs you want to keep for every scheduled job. The default is 5 runs.
181
Maximum number of days worth of log-files to keep (regardless of schedule): Enter the number of days you want to keep log files regardless of schedules. The default is 90 days. Tip: This defines parameters accordingly. If you define five days to retain and you are running scheduled jobs every day, even if you choose 10 runs, five of them are deleted.
Figure 5-22 Log-File Retention
5.6.1 Quota and constraint e-mail address rules

If a user exceeds the users quota or if the user reaches one of the defined constraint violation rules, TotalStorage Productivity Center for Data triggers an alert to notify the user. You can configure the e-mail address of the user for the notification. The elements you specify here are used to compose the e-mail addresses by the schema you define here. 1. Select Administrative Services Configuration Quota and Constraint e-mail Address Rules (see Figure 5-23 on page 183). 2. You can create an e-mail address based on the complete username, lastname, firstname, or substring of these values or any predefined text. 3. You can add variables before or after the cursor position, edit, or delete any values that are highlighted. a. To add, highlight the position and click Add After or Add Before. Select any of the following: USERNAME LASTNAME FIRSTNAME Text SUBSTRING of USERNAME,LASTNAME,FIRSTNAME
182
b. To edit, highlight the variable you want to edit and click Edit. You can edit only text variables. c. To delete, highlight any variable and click Delete.
Figure 5-23 Composing the way an e-mail address is formed
5.7 Scan/probe agent administration

You can assign agents that perform the scan against the volume or file systems of an NDS tree, NAS filers, and SAN File Systems (SAN FS). The window provides a complete list of: Licensed NetWare servers NetWare volumes discovered by TotalStorage Productivity Center for Data discovery jobs Licensed NAS filers Licensed SAN File Systems The steps are: 1. Select Administrative Services Configuration Scan/probe Agent Administration. If you do not have any machine of NAS filers, NDS tree, or SAN FS, the window does not show you anything and the rest of the steps are irrelevant for your environment. 2. You can either assign an agent to a single volume or to multiple volumes by highlighting the row or rows and by clicking Set Agent per row or Set agent for all selected rows.
183
3. You see the Filesystem Agent Editor window. Click the Scan/probe agent drop-down list and assign an agent to a selected volume. 4. Save to make the changes permanent.
5.7.1 Manual NAS/NetWare server entry

You can manually enter information about NetWare and NAS servers that you want to monitor. After adding it, you can assign an agent for the selected servers by using the procedure in the previous section. 1. Select Administrative Services Configuration Manual NAS/NetWare Server Entry. 2. To add an NAS server, click Add NAS server (Figure 5-24): a. A pop-up window appears. Fill in the parameters and press 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 SNMP protocol to contact and identify an NAS filer. Specify the login ID and password to log on to the NAS filer.
Figure 5-24 Adding NAS server
184
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 file system. d. To add NetWare server, click add NetWare server. e. A pop-up window appears. Fill in the parameters and press OK. Select the NDS tree. The NDS tree information is discovered by probe jobs that are run during agent installation. Enter the network name.
f. TotalStorage Productivity Center for Data contacts the NetWare Server and collects the volume or file system information of the NetWare server. g. Now, you can access the Scan/Probe Agent Administration window, and assign agents for the file system. h. To delete the information that you manually added, highlight the row and click Delete.
5.8 History aggregator

History aggregator runs in the Data Manager server and aggregates the data in the repository. You can configure the time that you want it to run. 1. Select Administrative Services Configuration History Aggregator, as shown in Figure 5-25. 2. In the When to Run tab, define the time and day of week in which the job will run, for example, run at 03:30 AM on each day except Monday.
Figure 5-25 Defining the time to run
185
3. In the Alert tab (Figure 5-26), define the action if the aggregator job fails. You can alert the following: Trigger a SNMP trap. Trigger a TEC event. Send a message to the user when the user logs on to the system. Write an event to the Windows event log as a warning or error. Run a predefined script on an agent machine by passing the Aggregator and job number. Send an e-mail to specified recipients.
Figure 5-26 Alert options
4. Check the Enabled box shown in Figure 5-25 on page 185 in the upper right corner of the window to make the aggregate job active.
186
Note: You must have previously defined SNMP, TEC, or an e-mail server for the alert to successfully run. 5. Save to make the changes permanent.
5.8.1 Data Manager NetWare tree logins

The probe job discovers the NetWare servers in your environment during Agent installation. In this window, you can edit NetWare server login information. TotalStorage Productivity Center for Data uses this login data to contact the NetWare server and collect necessary information about NetWare server. 1. Select Administrative Services Configuration NetWare Tree Logins. 2. Highlight the row and click Edit. 3. You can edit the following information: Discovering agent, select the agent from the drop-down list. Logon ID: Specify the fully qualified ID. This ID must have permission to enumerate the volumes in the NetWare server and to scan any selected file system. Password: Specify the password of the logon ID. 4. Save to make the changes permanent.
5.9 Data Manager CIMOM logins

Data Manager can show storage subsystem capacity summary information and disk, storage group, and LUN assets for storage devices. You need to install a CIMOM agent that can communicate with each storage device you want to manage and then configure that CIMOM agent in TotalStorage Productivity Center under Administrative Services Agents CIMOM. Data Manager Server communicates with the CIMOM server using TCP/IP by using the HTTPS/HTTP protocol. If the CIMOM and Data Manager server are on the same network subnet, Data Manager can automatically find the CIMOM server during a discovery job. You will see the configuration later.
5.9.1 Configuring CIMOMs

There are two ways of making the CIMOMs of your infrastructure known to the TotalStorage Productivity Center. Which one you use depends on how you have set up your CIMOM infrastructure.
187
If all your CIMOMs and the TotalStorage Productivity Center Server are located in the same subnet or if you have your CIMOMs distributed across multiple subnets and have set up a valid SLP infrastructure utilizing SLP Directory Agents, you can discover all of your CIMOMs automatically. Otherwise, you have to enter CIMOMs manually. We first try to do an automatic discovery to detect all CIMOMs, which are reachable through our SLP infrastructure. We then add the CIMOMs, which are still missing manually. To initiate an automatic CIMOM discovery, we select Administrative Services Discovery and click CIMOM (see Figure 5-27).
Figure 5-27 Configuring CIMOMs: initiate automatic CIMOM discovery
We now introduce a very important principle of operating the TotalStorage Productivity Center. We are now going to tell the TotalStorage Productivity Center to perform a certain task or action. Many of these actions or tasks are handled as special objects within the TotalStorage Productivity Center called jobs. We can define those jobs, save them, and run them at a later time, schedule them for a single or repeated runs, or run them at once.
CIMOM discovery job

In this case, we want the TotalStorage Productivity Center to discover CIMOMs, so we have to define a CIMOM discovery job. 1. Job definition works similarly for almost all types of jobs within TotalStorage Productivity Center. After selecting Discovery CIMOM job class in the Navigation Tree, you see three or more tabs in the Content Pane. In the first tab, the When to Run tab, you can define a schedule for the job. You can have
188
it run now, once at a later time, or multiple times. In this scenario, we select to run the job right now (see Figure 5-28).
Figure 5-28 Configuring CIMOMs: initiate automatic CIMOM discovery - When to Run
2. The next tab, the Alert tab, allows you to specify what to do when certain conditions for the job being defined arise at run time. For a CIMOM discovery job, there is only one condition for which you can define a reaction. You can specify what kind of Alerts TotalStorage Productivity Center triggers if the CIMOM discovery job fails. You find these first two tabs in most job definitions.
189
Figure 5-29 shows the Alert tab with the single condition for this job that we can choose, which is Job Failed.
Figure 5-29 Configuring CIMOMs - initiate automatic CIMOM discovery - Alert
3. In the last tab, which is the Options tab (Figure 5-30), you can enter information that is specific for the type of job 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 SVC Master Console (ITSOSVC), which we have configured as a SLP Directory Agent.
Figure 5-30 Configuring CIMOMs - initiate automatic CIMOM discovery - Enter DA addresses
190
4. You have now entered all information needed by the CIMOM discovery job to run successfully. We could now just save the job definition or save the job definition and have TotalStorage Productivity Center execute the job at that point in 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 bar. We see a message box that states that the CIMOM job has been successfully submitted (see Figure 5-31).
Figure 5-31 Job CIMOM submitted notice
Important: The CIMOM discovery is designed as a two-stage process. First, the CIMOM discovery job locates all 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 our case, 9.1.38.48). 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 managed by each CIMOM. Up to this time, 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. This is only successful for CIMOMs that have been set up to not require any user authentication. So it is highly likely that the first discovery job ends up with errors and with a status that the discovery and retrieval for the elements have succeeded only for few CIMOMs if for 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 we select Administrative Services Discovery CIMOM, we can view and change this job definition.
191
This job definition can run multiple times. Each run produces an entry below the Administrative Services Discovery CIMOM node of the Navigation Tree. This is the case for all types of jobs, and you see this mechanism implemented throughout the entire TotalStorage Productivity Center user interface. Because we have not just saved our CIMOM discovery job definition but have also started the execution of the job, TotalStorage Productivity Center has created an entry for your job.
Monitoring CIMOM Discovery job

1. We can view this entry by selecting Administrative Services Discovery CIMOM, right-clicking CIMOM, and selecting Refresh Job List from the drop-down menu. Then, expand the CIMOM node of the Navigation Tree. 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 competed with errors, and a green square indicates that the job has completed without errors. TotalStorage Productivity Center uses also a yellow triangle to indicate that a job has completed with warnings.
192
Figure 5-32 shows two entries. The upper one belongs to a job we ran earlier, and the lower one is the job we just submitted. The blue circle beside this entry indicates that the job is running. 2. If we click the entry of the job, we get a list of all logs for that job in the Content Pane. We can look at the logs by clicking the icon next to the log entry. This works even if the job has not yet finished but is still running.
Figure 5-32 Configuring CIMOMs: CIMOM discovery running
193
3. We can update the status of the job by right-clicking Administrative Services Discovery CIMOM and select Update Job Status. Note that the status does not update unless we refresh it this way. We finally see the following window, Figure 5-33, indicates that our discovery job has completed with errors.
Figure 5-33 Configuring CIMOMs: CIMOM discovery completed with errors
If we now examine the logs of the failed part of the job, we find that the errors are caused by failed logins, just as we expected. Note that other parts of the jobs have completed successfully. These are the logins and retrievals of information for the managed elements behind those CIMOMs, which do not require any authentication (in our example, the DS4000 CIMOM on the Colorado server). 4. Next, we look at which CIMOMs our discovery job has detected. We expand the Administrative Services Agents node of the Navigation Tree, right-click the CIMOM node, select Refresh, and then expand the CIMOM node. 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
194
marked by a green square and those CIMOMs for which no login could be established are marked by a red circle. Our CIMOM discovery job detected three CIMOMs. The DS4000 CIMOM was discovered over two ports (secure and non-secure). For this CIMOM, the login has been successful, and the information for the elements managed by this CIMOM could be retrieved. The other two CIMOMs are the DS-OPEN-API on the KLCH4VZ server (9.1.38.35) and the SVC CIMOM residing on the SVC Master Console ITSOSVC (9.1.38.38). Those CIMOMs require authentication, so the login to those CIMOMs has not been successful and TotalStorage Productivity Center could not retrieve the information for the managed elements (see Figure 5-34).
Figure 5-34 CIMOMs discovered using SLP by automatic discovery job
TotalStorage Productivity Center has now discovered three of our six CIMOMs and was able to log in to one of those three. Three CIMOMs are still missing.
195
User IDs and passwords

Now, the next task is to enter the user IDs and passwords for the two CIMOMs, which are already discovered and need authentication (SVC CIMOM and DS-Open-API) and manually enter the three missing CIMOMs. 1. We click the CIMOM entry in the Navigation Tree (Figure 5-35 shows the information for the DS-Open API CIMOM) and see all the information TotalStorage Productivity Center holds for the CIMOMs in the Content Pane. TotalStorage Productivity Center shows us a connection state (in our example below, we see LOGIN FAILED as expected). Enter the valid user ID and password as well as a display name. 2. We do this for each of our discovered CIMOMs.
Figure 5-35 Configuring CIMOMs: enter CIMOM user ID, password, and display name
3. We save these entries by selecting File Save in the menu bar. Note that we have ticked the check box Test CIMOM connectivity before updating. This causes TotalStorage Productivity Center to connect to the CIMOM and try to log in to it with the credentials we just have specified. If this is successful, the status indication of the CIMOM turns green. However, TotalStorage Productivity Center does not retrieve the information about the elements managed by this CIMOM. This requires another discovery job.
196
After updating all of our CIMOM definitions, we see the following window in Figure 5-36.
Figure 5-36 Configuring CIMOMs: configuration of automated CIMOMs complete
Manually entering CIMOMs

Next, we have to enter the three missing CIMOMs manually. 1. To do this, select Administrative Services Agents CIMOM and right-click CIMOM. Select Add CIMOM from the drop-down menu. TotalStorage Productivity Center shows us a dialog where the basic information about the CIMOM has to be entered, as shown in Figure 5-37 on page 198: IP address, port, and protocol (http or https) for the CIMOM Interoperability namespace (refer to the manufacturer of the CIMOM for the correct namespace. It is usually /root/ibm for IBM storage and tape systems). User ID and password for the CIMOM (if required) Display name (optional)
197
Figure 5-37 Configuring CIMOMs: add CIMOM dialog
2. After entering our missing CIMOMs, we see the following CIMOM entries under Administrative Services Agents CIMOM (see Figure 5-38).
Figure 5-38 Configuring CIMOMs: CIMOM configuration complete
198
Note: The Brocade CIMOM and the Engenio SMI-S connect using http and https over two different ports, so they appear 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, which 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 mean time). 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. This CIMOM discovery job now completes without errors and produces the output shown in Figure 5-39.
Figure 5-39 Configuring CIMOMs: second CIMOM discovery job completed successfully
Log files
We should now 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 default alert configured that raises an entry in the storage subsystem alert log each time a new storage subsystem is discovered.
199
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. Now, that we have successfully discovered all our storage subsystems, tape libraries, and switches behind our CIMOMs, we take a look if they show up in TotalStorage Productivity Center where they should.
5.10 Data Manager resource history retention

You can specify how long you want to keep the history of data in Data Manager repository. The longer you keep the data, the more information for the analysis is available, but on the other hand, the more space you need for the repository. 1. Select Administrative Services Configuration Resource History Retention. See Figure 5-40. 2. Clicking the check box activates the value of the related line. 3. You can select to not keep the history by clicking No History or by unchecking all boxes. 4. To get the default values, click Use Defaults.
Figure 5-40 Retain history
5. Save to make changes permanent.
200
5.10.1 Removed resource retention

This window allows you to specify how long to keep information in the repository for the values that are not in the system any longer. In other words, you can already remove some files from your system after the scan. In the next scan, TotalStorage Productivity Center for Data identifies those files as removed. By using a parameter in this window, TotalStorage Productivity Center for Data keeps them as long as you specified. 1. Select Administrative Services Configuration Removed Resource Retention. See Figure 5-41. 2. Select the appropriate check boxes to activate and adjust the value if needed.
Figure 5-41 Removed Resource Retention window
Note: Note that this window shows some elements that you do not have with an installation where only the Data Manager is in place. 3. Save to make the changes permanent.
201
5.10.2 Resource history retention for databases

You can specify how long you want to keep the history of data in the Data Manager repository for database tablespace and tables. The longer you keep the data, the more information for the analysis and also the more space you need for the repository. 1. Select Administrative Services Configuration Resource History Retention for Databases. See Figure 5-42. 2. Clicking the check box activates the value of the related line. 3. You can select to not keep the history by clicking No History or by unchecking all boxes. 4. To get the default values, click Use Defaults.
Figure 5-42 Retain History options window
5.10.3 Removed resource retention for databases

This window (Figure 5-43) allows you to specify how long to keep information in the repository for the values that are not in the system anymore. In other words, you can remove some tables from your database after the scan. In the next scan, TotalStorage Productivity Center for Data identifies those files as being removed. By using the parameter in this window, TotalStorage Productivity Center for Data keeps them as long as you specified. 1. Select Administrative Services Configuration Removed Resource Retention for Databases. 2. Click the check box to activate the value.
Figure 5-43 Retain removed databases
202
3. Save to make changes permanent.
5.10.4 Adding databases

In general, when an agent is registered to TotalStorage Productivity Center for Data, by default, it only reports its file system storage assets. To use the database reporting of TotalStorage Productivity Center for Data as well, all agents, which run for database reports, must be registered using the Databases portion of the License Key Editor. If there are databases running that you want to monitor, you need to manually register your databases and then you can run jobs against your agents to report the databases. To do that: 1. Select Administrative Services Configuration License Keys. 2. Click the magnifying glass icon to the left of the line for IBM TPC for Data-Databases, as shown in Figure 5-44.
Figure 5-44 License Keys IBM TPC for Data: Databases
3. In the Licensing tab, agents are displayed. Click the RDBMS logins tab. 4. Initially, there should not be any entries for a computer. Click Add new. 5. The RDBMS Login Editor pop-up window appears (Figure 5-45 on page 204). Type the values accordingly: For Oracle: Select the agent where Oracle runs. Enter the Oracle SID ID. Type the Oracle Host name. Specify the Username 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 a different port number, contact your Oracle specialist to obtain the correct port number and type in the correct port number.
203
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. Instance of SQL server. If it is left blank, TotalStorage Productivity Center for Data uses the default instance. Username and password of SQL server instance. The default port is 1433. JDBC driver. Select the agent where Sybase or DB2 runs. Instance or server name of Sybase and DB2. Username and password of Sybase or DB2 instance. The default port for Sybase is 5000 and for DB2 is 50000.
For Microsoft SQL Server:
For Sybase and IBM UDB DB2:
Figure 5-45 RDBMS Login Editor window
Click Save to continue. TotalStorage Productivity Center for Data contacts the database immediately and registers the database to TotalStorage Productivity Center for Data repository and also runs a probe job for the selected agent. Figure 5-46 on page 205 shows two computers with databases running on them.
204
Figure 5-46 Database information
6. You can now edit or delete the database entry by highlighting the line and clicking Edit or Delete. If you edit, then you can only change Username, password, and port number.
205
5.11 Configuring chargeback

If you are running an IT infrastructure where you are hosting multiple client environments, or if you just want to charge the departments in your own environment by monitoring their usage, you must configure Chargeback by doing the following: 1. Select Data Manager for Chargeback Parameter Definition (Figure 5-47).
Figure 5-47 Chargeback configuration
2. First, select the output invoice format. There are two invoice formats that you can produce. One is the default, TotalStorage Productivity Center for Data format (Figure 5-48 on page 207), and the second one is the standard CIMS format (Figure 5-49 on page 207).
206
Figure 5-48 Chargeback sample invoice
Figure 5-49 Chargeback data format
207
3. You can charge your client or department by editing the following consumption values: Operating System Storage usage by user. Output is based on users in your environment. Operating System Disk capacity by computer. Storage Usage by database user. Total Size by database-tablespace.
208
Chapter 6.
Administration
This chapter provides information about all administration tasks that are necessary to keep IBM TotalStorage Productivity Center running. We describe how to work with the user interface. In this chapter, the following topics are discussed: Using Data Manager Report function of the Data Manager Data Manager Navigation Tree path Reporting facility
209
6.1 Using Data Manager

The Data Manager server is the main 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, file systems, allocated files, file characteristics, such as the size of the file, duplicate files, orphan files, obsolete files, and backup information of these files. Data Manager server has a powerful scheduler to submit several jobs, such as discovery, ping, probe, and scan. In this chapter, we show you how to use the functions of Data Manager Server through its GUI.
6.1.1 Starting the user interface

The Data Manager user interface consists of two primary components: The explorer-like tree view on the left and the window on the right side, where all the content is displayed.
Navigation tree
The navigation tree appears on the left of the screen, and you can expand, select, or collapse the tree. Figure 6-1 on page 211 shows some of the Navigation Tree elements we discuss in this chapter. You can expand and collapse the necessary levels depending on the task you are working on. Related functions are bundled in groups.
210
Figure 6-1 TotalStorage Productivity Center Navigation Tree
These are the primary groups of the Navigation Tree relating to TotalStorage Productivity Center for Data: Administrative Services: Mainly used for configuration of TotalStorage Productivity Center for Data itself 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 Data Manager server. Agents: Used to control and view various agent components that are running on the monitored machines in your environment. Discovery: Used to create, submit, and monitor CIMOM discovery jobs.
Chapter 6. Administration
211
Configuration: Used to allow the system administrator to tune the settings that control various operational characteristics of Data Manager. 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 panel
The Content panel appears on the right of the Navigation Tree pane. When you select functions from the Navigation Tree pane, a corresponding window appears in the Content panel. You add, change, delete, create, and fill in the values by using functions in the Content panel. Because the content of the Content panel changes with the function selected, we see several Content panels throughout this chapter (Figure 6-2).
Figure 6-2 Content panel - Data agent example
212
6.1.2 Administrative services

You use this section for administrative purposes (Figure 6-3). It allows you to monitor internal jobs, the status of components within Data Manager Server, and the configuration of the server. There are four elements that you can work on.
Figure 6-3 Administrative services
Services
When you expand Services, you see the five services of the Data Manager server (Figure 6-4).
Figure 6-4 Data Server and its five main services
213
Double-click Server and you see the following information for your Data Manager server in the Content panel (see Figure 6-5 on page 215): 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 Total Online Offline Unreachable Upgrading Upgrade required
Agents
The important values in this window are: Number of agents and whether they are offline, unreachable, or need an upgrade Number of pending requests
214
Figure 6-5 Server information - details
Double-clicking Scheduler, GUI, or Agent gives you the following information: Service status Pending request Processed request Idle threads The important values in this window (see Figure 6-6) are: Service status (it should be active.) Number of pending requests
Figure 6-6 Scheduler information
215
If you right-click when your cursor is on one of the Scheduler, GUI, or Agent services icons, you see additional functions, as shown in Figure 6-7.
Figure 6-7 Additional functions
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 agent component: C:\program Files\IBM\TPC\Data\log\TPCD_xxxxxx.log Figure 6-8 on page 217 shows a sample Scheduler log display in the Content panel.
216
Figure 6-8 Log and errors
Configure tracing by right-clicking the desired service and selecting Configure Tracing. When reporting a problem, you might be asked to produce a trace related to that service. In that case, you should enable the trace and provide the report to the support center for debugging. On this window, you can enable the trace and define the trace level as DEBUG_MIN, DEBUG_MID, or DEBUG_MAX.
217
Figure 6-9 shows the Configure Tracing pop-up window for the GUI and the Server. Note that the Server Tracing configuration allows you to also specify the number and size of the trace logs. The following is the path and naming convention for the Trace log files. The Server component is shown as an example: C:\Program Files\IBM\TPC\Data\log\ServerTrace.log
Figure 6-9 Trace configuration
Shutdown: There are three options to shut down the service. Normal: Service is shut down cleanly. It lets all running processes complete and accepts any new request. Shutdown takes place if there is no new request and all running processes finish. Immediate: Service is shut down immediately. It lets all running processes complete, but 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 Immediate option. To restart the service, right-click the service and select the Start option.
Agents
When you expand Services, 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. When you click one of the agents, you
218
see information about the agent in the Content panel in three different tabs, as shown in Figure 6-10.
Figure 6-10 Administrative Service - Agents window - one Agent selected
The General tab

The following information is available (Figure 6-11 on page 220): Agent status Port Host Address Last update Timezone Connection Errors Consecutive Errors The important values are the status of agents and errors.
219
Figure 6-11 Agent information
The Detail tab

The following information is available (Figure 6-12): Agent name Host name Start Time Elapsed Time VM Size Manufacturer OS Type CPU Architecture Job Count
Figure 6-12 Detailed agent information
220
Jobs
If there is any job that is currently running for this agent, you can see the following information (Figure 6-13): Schedule name Job name Run Job Status Scheduled time Started time
Figure 6-13 Scheduled job information
6.2 Report function of the Data Manager

This section describes the reporting function of the Data Manager component of the TotalStorage Productivity Center. It provides information about the predefined reports and how to generate them.
221
6.2.1 Predefined reports under the My Reports node

Navigate to IBM TotalStorage Productivity Center My Reports System Reports Data and expand the node, as shown in Figure 6-14.
Figure 6-14 Predefined reports
Data Manager enables us to generate and use reports easily by using the predefined reports in the section My Reports. It is divided into the following subnodes. Note: Not all of the possible reports are shown in detail in this section. For certain reports, we only give you a textual description of how to generate the reports or a short description of what the purpose of the report is.
System reports
These reports are predefined within 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. Examples of selected predefined reports are shown.
222
When the reports are displayed in the Content panel, you see either a pie-chart icon, a magnifying glass icon, or both. Clicking the pie chart icon displays the report in a graphical pie chart. Clicking the magnifying glass gives you the report details in a tabular form.
Access Time Summary report

This report provides a summary of a number of files depending on when they were last accessed and provides the following information about the files (see Figure 6-15): The number and size of the files, which are accessed between several different time periods Total number of files accessed
Figure 6-15 System access time reports
223
Complete the following steps to generate a report for all of your servers: 1. Select IBM Total Storage Productivity Center My Reports System reports Data Access Time Summary (see Figure 6-16).
Figure 6-16 Access Time Summary report
2. Click the Selection tab in the top left of the Report Filter Specifications. 3. Select the profile and columns to include or exclude and click Generate Report. 4. The first report is Network-wide, as shown in Figure 6-17.
Figure 6-17 Access Time Summary report - Network-wide
5. Click the Pie Chart Icon to view the report in the Pie Chart format, as shown in Figure 6-18 on page 225.
224
Figure 6-18 Pie chart of Access Time - Network-wide
To generate a report for an individual server, complete the following steps: 1. Select IBM Total Storage Productivity Center My Reports System reports Data Access Time Summary. 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 6-19.
Figure 6-19 Access Time Summary - network-wide servers
225
5. Click the magnifying glass icon or pie chart icon next to the server to see the report for the selected server, as shown in Figure 6-20.
Figure 6-20 Report for an individual server
Disk Capacity Summary report

This report shows the disk capacity of the servers. This report can give you the following information about the disk capacity: The total capacity of disks The amount of used space on disk The amount of free space on disk Raw volume space The amount of space used by 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, as shown in Figure 6-21.
Figure 6-21 Disk Capacity Summary report
2. Click the Selection tab in the top left of the Report Filter Specification, as shown in Figure 6-22 on page 227.
226
Figure 6-22 Disk Capacity Summary - Report Filter Specification
3. Select columns to include or exclude and click Generate Report. 4. The first report is network-wide. 5. Click the magnifying glass icon or pie chart icon next to each line to see the report for the selected server.
Figure 6-23 Disk capacity summary
227
Access File Summary report

This report provides overview information of files in the monitored servers. The following details are available: The total size of files The number of files The number of directories Average size of files The capacity of the file system
Storage Access Time report

This report provides information about files that were last accessed. The following details are available: The name of the computer on which the file is stored Several different time periods that the file was last accessed
Disk Defects report

This report provides disk defect information for the monitored servers. The following details are available: The name of the computer that has the disk defects The number of defects detected Disk RPM Capacity of disk and unallocated space The number of recovered and unrecovered errors Bytes written and read to disk You can generate a report by completing the following steps: 1. Select IBM Total Storage Productivity Center My Reports System reports Data Disk Defects, as shown in Figure 6-24 on page 229.
228
Figure 6-24 Disk Defects report - Report Filter Specifications
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.
229
4. Click the magnifying glass icon or line chart icon next to each line to see the report for the selected server, as shown in Figure 6-25.
Figure 6-25 Disk Defects report - by Disk and computer
Storage Modification Times report

This report provides information about files written within the network that were modified: Within the last 24 hours Between one week to one month previous Between one month to one year previous More than one year previous
Most at Risk Files report

This report shows files that have been modified but have not been backed up for a long time. Later, you can use this information to back up and archive the files automatically using Tivoli Storage Manager server. The following details are available: The name of the file, computer, and path name The create, modified, and access date and time of the file The owner of the file The size of files (logical + physical) You can generate this report by using the following steps: 1. Select IBM Total Storage Productivity Center My Reports System reports Data Most at risk files.
230
2. Click the Selection tab in the top left of the Report Filter Specifications, as shown in Figure 6-26.
Figure 6-26 Most at Risk Files report - Report Filter Specifications
3. Select profile and the number of rows for each computer. Then select the columns to include and exclude, and click Generate Report.
231
4. The report shows you the oldest files, which have been modified but not backed up. It is sorted by computer name, as shown in Figure 6-26 on page 231.
Figure 6-27 Most at Risk Report - by computer
5. You can also select the computers from the list or perform filtering depending on the columns available.
Tivoli Storage Manager backup and archive from Most at Risk files
To initiate backup and archive to the Tivoli Storage Manager server, perform the following steps: 1. Highlight the line or lines for each file. You can use the Shift key to select a group of files or the Ctrl key to select an individual file, as shown in Figure 6-28 on page 233.
232
Figure 6-28 Select files to back up from Most at Risk Files report
2. Right-click and the Selection pop-up window appears (see Figure 6-29): a. Select Create a new archive/backup job to run a new job. b. Select Add to an existing archive/backup to add the list to an already created job.
Figure 6-29 Most at Risk Report - Tivoli Storage Manager options
233
3. Select the type of backup you want to run (see Figure 6-30): Archive Selective backup (Full backup) Incremental backup
Figure 6-30 Create File Archive/Backup Action
4. Define any extra options for the Tivoli Storage Manager server by selecting the appropriate tabs. Figure 6-31 on page 235 shows the options under the When to Run tab, and Figure 6-32 on page 235 shows the Alert tab options.
234
Figure 6-31 When to Run tab options
Figure 6-32 Tivoli Storage Manager Create File Archive/Backup Action - Alert options
235
5. Press Ctrl-S to save or save to create the job. 6. You can follow the job status from Data Manager Policy Management Archive/backup Job name.
Most Obsolete Files report

This report provides information for files that have not been accessed or modified for a long time.
Oldest Orphaned Files report

This report provides information for files that are not owned by any user. You can take a backup and archive of these files by using the same procedures that are mentioned in Most at Risk Files section.
User Quota Violations report

This report provides information for users who have violated the quota defined by you (see Figure 6-33). The following details are available: Quota creator Quota name User who violate the quota Space used by user that exceeds the quota Tip: You need to define quota in advance in order to have reports for quota violation. No data is displayed if there is no quota defined or there is no violation.
Figure 6-33 Quota violations
236
Storage Availability report

This report provides information about the availability of computers that are monitored using the PING job.
Storage Capacity report

This report provides storage capacity information about each computer, as shown in Figure 6-34.
Figure 6-34 Disk capacity
Total Free Space report

This report provides the amount of unused storage capacity in your environment.
User Space Usage report

This report provides storage usage, based on the user, on the server and storage capacity information about each computer.
237
Wasted Space report

This report provides information about storage used by files that are not owned by an operating system and have not been accessed for one year, as shown in Figure 6-35.
Figure 6-35 Wasted space summary
6.2.2 Batch reports

The batch reporting feature enables you to run any report on a regularly scheduled basis. This enables you to conveniently run reports and gather data on a set schedule. To create the batch report, perform the following steps: 1. Select IBM Total Storage Productivity Center My Reports Batch Reports. 2. Right-click and select Create Batch Report, as shown in Figure 6-36.
Figure 6-36 Batch report options
3. Select the report type, as shown in Figure 6-37 on page 239. You can select the following reports: Asset System-wide Storage Subsystems Availability Capacity Usage
238
Usage Violations Backup
Figure 6-37 Batch report types
239
4. Click the Options tab to define the batch output, as shown in Figure 6-38. The options include: Select Agent computer to run the batch report job. Select output format: CSV Formatted File HTML File
Figure 6-38 Batch report options
Select the format for the output file name (see Example 6-1).
Example 6-1 Batch report format {Report creator}.{Report name}.{report run number} TR50411.batch-report1.001.HTML
5. Click When to Report to define the schedule time.
240
6. Press Ctrl-S to save the batch report. The job will be submitted at the specified time and day. You can follow the status by selecting Data Manager My Reports Batch Reports. 7. The batch report output is saved to the specific directory of the agent machine with the name that you specified in the Options tab. For Windows, the output is saved in: \Program Files\IBM\TPC\ca\subagents\TPC\Data\log\computername\reports\ For UNIX, the output is saved in: /opt/IBM/TPC/ca/subagents/TPC/Data/log/computername/reports/
6.2.3 Creating Probes

Probe jobs collect detailed statistics about all the assets of the managed infrastructure, such as computers, disk controllers, hard disks, clusters, fabrics, storage subsystems, LUNs, tape libraries, and file systems. Probe jobs can also discover information about new or removed disks and file systems. 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 add computer, computer groups, clusters, storage subsystem groups, or storage subsystems for the probe job to run. 4. You can create separate probe jobs for different groups. 5. Select job schedule characteristics, such as run immediately, or 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.
241
Figure 6-39 embodies all of the elements of the probe job in one window.
Figure 6-39 Create a probe job
242
6.2.4 Topology Viewer

One new feature of TotalStorage Productivity Center Version 3.1 is the Topology Viewer. Its purpose is to display the whole storage infrastructure in a graphical, easy to interpret way. For completeness, we have included a sample of the Topology Viewer in Figure 6-40.
Figure 6-40 Topology Viewer - Overview
243
6.3 Data Manager Navigation Tree path

Now that we have reviewed the first part of the Data Manager function, which is located under the IBM TotalStorage Productivity Center node in the Navigation Tree, we can scroll down to the Data Manager node. These are the functions in the so-called Data Manager Main Menu, as shown in Figure 6-41.
Figure 6-41 Data Manager Main Menu
6.3.1 Monitoring
The monitoring function enables us to run regularly scheduled data collection jobs. These jobs gather statistics about storage assets and usage within the environment. The following sub-functions are available.
Groups
A group represents a set of user-defined objects against which you can run monitoring and reporting jobs. This section describes the possible groupings.
244
Computer
A computer group is a logical grouping for related computers. To create a computer group, perform the following steps: 1. Select Data Manager Monitoring Groups Computer. 2. Right-click and select Create Computer Group. 3. All Available computers are listed. 4. Double-click computers to add a computer to the group under Current Selections. 5. Press Ctrl-S to save the group with a new name. A pop-up window asks for the name of the group (see Figure 6-42). Edit the name and press OK.
Figure 6-42 Grouping computers
Filesystem
The filesystem group is a grouping of file systems in computers. To create the filesystem group, perform the following steps: 1. Select Data Manager Monitoring Groups Filesystem 2. Right-click and select Create Filesystem Group. 3. The list of Available computers and their file systems displays. 4. Expand the computer name to display the file system names. 5. Double-click the file system name to include in the group. 6. Press Ctrl-S to create the group.
245
Figure 6-43 Grouping file systems
Directory
A directory group is the grouping of directories in computers. To create the directory group, complete the following steps: 1. Select Data Manager Monitoring Groups Directory. 2. Right-click and select Create Directory Group. 3. Click New Computer. 4. The Edit directories for computer pop-up window appears. 5. Select the computer or all-computers. 6. Edit the directory name and click Add. Attention: TotalStorage Productivity Center for Data does not check the syntax or whether the directory is available. So be careful to add the directories that are actually available. Otherwise, the group reports for the group do not contain any data. 7. For another directorys information, repeat Steps 3 to 6. 8. Each time when you add a directory for a computer, the computer information does not display on the next Edit directories for computer window. To add a new directory to the computer, you have to do the following steps: a. Click the computer name and right-click. b. Select Edit.
246
c. The Edit directories for computers pop-up window appears for the selected computer. d. Add a new directory and press OK. 9. When all directories are added, press Ctrl-S to save the grouping information (see Figure 6-44).
Figure 6-44 Grouping Directory
User
This function groups users on all computers.
OS user group
The OS user group is a grouping of users defined in the operating system as a user group.
247
6.3.2 Pings
The Ping job collects information about the availability of the storage assets in your environment. To create the Ping job, complete the following steps: 1. Select Data Manager Monitoring Pings. 2. Right-click and select Create Ping. 3. You can add a computer, computer groups, or clusters for the Ping job to run against (see Figure 6-45).
Figure 6-45 Create a Ping job
4. You can create separate Ping jobs for different groups, if you want, for example, one Ping job for computers that have DB2 and one Ping job for Linux computers. 5. Select job schedule characteristics, such as run immediately, run once at a certain time, or run several times. 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 6-46 on page 249.
248
Figure 6-46 Ping job status
6.3.3 Creating Scans

The Scan job collects statistics on the usage of storage. Detailed usage information is restored to the Data Manager repository. To create the Scan job, perform the following steps: 1. Select Data Manager Monitoring Scans. 2. Right-click and select Create Scan. 3. You can add file systems, a computer, computer groups, or clusters to the scan job, which runs as shown in Figure 6-47.
Figure 6-47 Create Scan job
249
4. You can add specific directories to the scan job: a. Click the Directory Groups tabs. 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 and add the directory for the selected computer. Press Add. e. Click OK and save the directory group by pressing Ctrl-S. 5. Select the Profile tab to customize the Scan job, as shown in Figure 6-48.
Figure 6-48 Scan job Profile selection
6. 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. 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. See Figure 6-49 on page 253.
250
6.3.4 Profiles
A Profile enables 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 6-1.
Table 6-1 List of Profiles Description Statistic about the number of files that are modified (longest) but not backed up since modified (20 files are the default) (Windows only). Statistics about the file based on their access time. Statistics about the file based on their creation time (Windows only). Statistic about files that are modified but not backed up since the modification (Windows only). Statistics about files by length of time since last modification. Information about the size of the files. Statistics for the number of largest directories (20 directories are the default). Statistics for the number of largest files (20 files are the default). Statistics for the number of largest orphans. Orphans are the files that have no owner since they were created (20 files are the default). Statistics for the number of most obsolete files. Obsolete files are the files that have not been modified or accessed for a long time (20 files are the default). Statistics for the number of oldest orphans (20 file is the default). Summary based on file type. Summary based on filesystem/directory. Summary based on groups. Summary based on owner.
Profile name Most At Risk
By Access By Creation By Mod Not Backed Up By Modification File Size Distribution Largest Directories Largest Files Largest Orphans
Most Obsolete Files
Oldest Orphans Summary By File Type Summary By Filesystem/Directory Summary By Group Summary By Owner
251
Profile name Temporary Files Wasted Space
Description Statistics for files that are not owned by the operating system and have not been not accessed in one year. Statistics for space usage for space that is not owned by the operating system and has not been accessed in one year.
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 to be included in the Profile (see Figure 6-49 on page 253): a. Summary space usage by: Filesystem Owner Group File types b. Gather statistics by length of time since: Last access Creation Last modification Last modification (not backed up) c. Gather information about the: Size of the distribution Largest file Largest directories Most obsolete files Most at risk files Largest orphaned files Oldest orphaned files 4. Optionally, define the number of files to gather information about.
252
Figure 6-49 Creating Profiles
5. Press Ctrl-S to save and create the Profile. Continue to use these windows if you want to create more profiles with your own definitions.
6.3.5 Alerting
Alerting is used to inform the TPC administrator when certain conditions occur on the devices that are monitored. TotalStorage Productivity Center for Data collects statistics for the computer, storage subsystems, file systems, and directories. You can set certain thresholds to detect the problem or events that might create problems later, so that storage administrators can be proactive in correcting potential problems. The general approach to using the alerting function is to create an alert definition, which has been described several times in relation to the creation of Monitoring jobs. Because it is similar to all of the other types of alerts, we do not go into a lot of detail here. To create an alert, navigate to the Data Manager Alerting Computer Alerts node in the Navigation Tree.
253
Right-click and select Create Alert, as shown in Figure 6-50.
Figure 6-50 Create an alert
The next window, Figure 6-51, shown to you is the general alert definition window.
Figure 6-51 The general Create alert window
254
When you select the Alert tab, you can use the Condition drop-down list to select one of the following alert types, as shown in Figure 6-52.
Figure 6-52 Select an alert type you need
255
After you have selected the type of alert you need, you should go back to the Computer tab and make an association of the alert to one or more of your resources, as shown in Figure 6-53.
Figure 6-53 Always make an association with a resource
This sequence completes the introduction of how to create an alert. The principle is the same with any other type of alert throughout this IBM Redbook. Alerting can be set on the following statistics. That means you define a threshold or state, which should be reported on your resource, and if the threshold or state is not as expected, TotalStorage Productivity Center raises an alert, based to your definition.
Computer alerts
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
256
Virtual server added Virtual server removed Virtual server moved Computer Unreachable Computer Discovered Computer Status Change Offline Computer Status Change Online Computer Property Change HBA Driver Version Change HBA Firmware Version Change You can select only one condition at a time. If you want to detect several conditions, you have to define separate alerts for each condition.
Multiple condition alert

Let us define an alert for two separate conditions, one for Disk not found and one for RAM Decreased. Perform the following steps to create the alerts: 1. Select Data Manager Alerting Computer Alerts. 2. Right-click and select Create Alert. 3. Select RAM Decreased from the condition list. 4. Click the Computers tab and select which machines are detected. 5. Press Ctrl-S to save the alert. 6. Repeat Steps 1 and 2. And this time, select Disk not found from the list. 7. Repeat Steps 4 and 5.
File system alerts

These alerts are detected by the Scan job. 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 FS Inode less than X (percentage or inodes) You have to enter a threshold value for this condition Let us define an alert for Filesystem freespace less than 30 percent. Complete the following steps to create the alerts: 1. Select Data Manager Alerting Filesystem Alerts.
257
2. Right-click and select Create Alert. 3. Select Filesystem Freespace less than from the condition list (see Figure 6-54). 4. Edit 30 for the Value and select Percent from the list. 5. Click the Filesystems tab and select which machines are to detected. 6. Press Ctrl-S to save the alert.
Figure 6-54 Creating Filesystem alerts
Directory alerts
These alerts are detected by the Scan job. 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. Let us define an alert for Filesystem freespace less than 10 Gb. Complete the following steps to create the alerts: 1. Select Data Manager Alerting Directory Alerts. 2. Right-click and select Create Alert. 3. Select Directory consumes more than from the condition list. 4. Edit 10 for the value and select Gigabytes from the list. 5. Click the Directories tab and select which machines are to be detected. 6. Press Ctrl-S to save the alert.
258
All alerts that you define are written to one that you defined for Triggered-actions and also to the Alert Log. 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 filesystem alert with the Filesystem freespace less than 200 Gb condition and ran the Probe job. One of the computers, which met the alert condition, has been detected. The following steps take you to the alert log: 1. Select IBM TotalStorage Productivity Center Alerting Alert Log. 2. Select All or Filesystem from the subtree. 3. The report displays if there is at least one machine that satisfies the alert condition: a. Check the alert type to see the condition. b. Check the alert name and alert creator to see which alerts have been satisfied. 4. In our example (see Figure 6-55), Filesystem Alert has detected a Data free space low condition.
Figure 6-55 Filesystem alert
5. To get more information, click the magnifying glass icon (see Figure 6-56).
Figure 6-56 Detailed alert information
259
6.3.6 Policy management

With this feature, we have another powerful ability to manage our monitored servers by applying policies, such as setting quotas, constraints, running scripts, taking automatic backups, or even extending the file system automatically. The following policy managements shown in Figure 6-57 are available.
Figure 6-57 Policy Management node in the explorer view
As you can see, there are six areas regarding the policy management: Quotas Network Appliance Quotas Constraints Filesystem Extension Scheduled Actions Archive/Backup In general, you should note the following: If there is a plus sign in front, there are either more browsable items or user-defined entries already. If there is no plus sign in front, there is not yet a user-defined entry. With policy management, we have no predefined definition of any type.
260
Quotas
You can set limits on the amount of storage that a user or 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 different levels: Network Level Computer Level Filesystem Level They are available for single Users or OS User Groups. With this ability, a user can only consume that which is allowed and at the same time, you can allow a user to consume more storage on one computer while limiting that user to consuming less on another computer. And in total, you can limit a user to consume a specified 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 quotas 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 or 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 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, edit the value to 100 Gb. 9. Schedule the job by selecting the When to Run tab.
261
Note: Only after the next scan runs successfully is the information, according to the current situation in the file system, gathered and written into the Data Manager repository. To have an up-to-date file system as opposed to quota information, plan to run the quota job after the scan job. The Data Manager then compares the file system information against the defined quotas. 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 (see Figure 6-58).
Figure 6-58 Quota for Computer job
12.To see the list of users who have violated the quotas, select IBM Total Storage Productivity Center Alerting Alert Log All as shown in Figure 6-59.
Figure 6-59 Quota alert details
262
Network appliance quotas

You can also use the NAS support within Data Manager to work with Quotas defined using the software provided with Network Appliance Filers. Using the Network Appliance node under Policy Management, you can: Import certain Quotas from NetApp filers when you schedule and run a Quota checking job. View the definition for each imported Quota. Determine when and how you are alerted when the hard limit defined with a NetApp Quota is close to being violated. For example, you can define a policy to be alerted when: A user or user group is close to reaching the hard limit defined within the corresponding NetApp Quota. The space consumed on a QTree is approaching the hard limit defined within the corresponding NetApp Quota. Specifically, the Data Manager NAS component enables you to work with the following types of Network Appliance Quotas: Quotas that limit the space that QTree directories can consume on a volume Quotas that limit the space consumed by specific users on a volume Quotas that limit the space consumed by specific user groups on a volume
Constraints
Constraints are used to limit the user from putting restricted or unacceptable file types on the monitored machines. 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.
263
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 6-60.
Figure 6-60 Constraint file types
5. Click the Users tab. You can either Forbid or Allow certain file types owned by selected users (see Figure 6-61 on page 265).
264
Figure 6-61 Constraint users
6. Click the Options tab (Figure 6-62). You can set up 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 since they were modified in more than a specified number of days.
Figure 6-62 Constraint options
7. All of the constraints that you have selected in the previous three steps can be seen in File Filter Text in the Options window. You can directly add new conditions or change the previously set conditions from this window. Here are some examples: a. (NAME matches any of ('*.avi', '*.jpg', 'itso*.*') AND TYPE <> DIRECTORY) Restrict files that match a certain file pattern.
265
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. To add a new condition, do the following steps: a. In the Options window, click Edit Filter. b. The Edit Filter pop-up window appears (Figure 6-63 on page 267). c. Highlight the line and right-click. The following options display: New Condition New Group Merge Edit Delete Cut Copy Paste
266
Figure 6-63 Adding a new condition
d. Click New Condition. A Create Condition pop-up window appears (see Figure 6-64).
Figure 6-64 Condition options
267
e. A pop-up window is context sensitive. Depending on the selected condition, the window changes accordingly. f. As an example, select Name, edit 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. 8. Click the Alert tab to set the triggering-condition. 9. 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. But Scheduled actions can be run whenever you want without waiting for an alert condition. Scripts work in the following way: 1. During installation, TotalStorage Productivity Center for Data creates the following directory on every server and agent machine: \Program Files\Tivoli\ep\Subagents\TPC\Data\Scripts for Windows agent /usr/tivoli/ep/subagents/TPC/Data/scripts for UNIX agent \Program Files\IBM\TPC\Data\Scripts for Windows server /usr/IBM/TPC/Data/Scripts for UNIX server 2. When the scripts run, TotalStorage Productivity Center for Data checks the local script directory. 3. If the server finds the script, it loads it and sends it to the agent machine. 4. The agent checks its local script directory. 5. If the agent finds any local version, then 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, then 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 scripts.
268
Important: If the script that you prepare on the server does not run, then check the following: 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 pull-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. 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.
269
Archive/Backup
You can use Tivoli Storage Manager to archive or back up files. From this window, shown in Figure 6-65, you can only update, delete, or run the jobs that have already been created using a slightly different method. The following pop-up window displays if you try to create a backup by right-clicking Archive/Backup.
Figure 6-65 Pop-up window when right-clicking Archive/Backup
The way an Archive or Backup job is defined is different than the others. These types of jobs are defined on the files you found as a result from a certain report. That means that you have to define a report, which is able to determine a list of files, and on that list of files you are creating the Tivoli Storage Manager Backup or Archive job. These jobs are displayed and managed from here.
6.4 Reporting facility

The reporting facility uses the data in the repository. That means every report, either one of the 300 predefined reports or a report that you define, is based on the data, which is already in the repository database. Reports can be displayed as a table or as a graphical chart. Data can be extracted at different levels, such as computers, storage subsystems, files, users, and so on. The following major sections are available: Groups Asset Availability Capacity Usage Usage Violations Backup
270
To better demonstrate all of the different reporting types, refer to Figure 6-66. Note that not all entries are fully expanded.
Figure 6-66 The various reporting areas
Generally, keep in mind 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 a different scope, that is, you define the report to run on a single computer, the reports are going to be run in one of the following two ways: Run this report just once. Save the report definition and the report shows up under the MyReports section in the Navigation Tree view.
271
6.4.1 Groups
Groups are a means to define subsequently defined reports against these groups of computers or file system groups. The advantage is that you easily can handle many computers in just one predefined group. As described earlier, the way to define this type of group follows the same principle and is not detailed any further.
6.4.2 Assets
TotalStorage Productivity Center for Data can be used as a central repository for your assets in the environment. Probe jobs extract asset information from each computer and save the information in the repository. Then you can select several subreports to view the asset information of the computer. Assets can be seen based on Cluster, Computer, OS type, Storage Subsystem, or System-wide. The following are the Asset major categories and subcategories: Note: Within the Asset subtree, all of the available selections display the related information about 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 shows the assets based on MSCS cluster membership. Clusters are subdivided into nodes and virtual servers. For each virtual server, you can see controllers, disks, file systems, logical volumes, and exports or shares.
By Computer
Each computer in the environment is listed. Depending on computer operating system type, each computer is subdivided into controllers, disks, volume groups, file systems, exports or shares, and monitored directories. Here is an example for AIX, Linux, or Windows computers. 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 AZOV.almaden.ibm.com (see Figure 6-67 on page 273).
272
Figure 6-67 Computer report
The report displays detailed information about the machines architecture and storage as soon as you select the computer.
273
3. To get detailed information for each component of a machine, you can select the following subtrees: a. Controllers: This lists the built-in controllers of the machine. Click the controller name to get information for the controller (see Figure 6-68).
Figure 6-68 Controller overview and details
b. Disks: This lists the number of disks that you have attached to your computer (see Figure 6-69).
Figure 6-69 Disk overview
Click one of the disk definitions to get more information about it.
274
Figure 6-70 Detailed disk information
Five tabs display: General: The window displays information about the disk and allocations on the disk. Paths: This shows how the disk is seen from the operating system point of view. Latest Probe: This is information gathered during the last probe, such as the physical characteristics of the disk (RPM, sector size, heads, and cylinders), defects, and errors detected (see Figure 6-71 on page 276). Probe History: This shows all the probe jobs that were run for this machine since installation. LUN Definition: If the CIMOM agent has been configured, then the disk subsystem reports its LUN configuration.
275
Figure 6-71 Information by last probe
c. Volume Groups: This 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 file system on the volume group (see Figure 6-72).
Figure 6-72 Detailed Volume groups
276
d. Filesystems or Logical volumes: This lists the file systems and logical volumes on the selected computer. See Figure 6-73. Two tabs are available: Filesystems: This shows you the information about the file system, such as capacity and number of inodes, and the scan jobs and probe jobs that are run for the selected computer.
Figure 6-73 Filesystem logical view
Logical Volumes: This shows us the volume, which constructs the file system. See Figure 6-74.
Figure 6-74 Logical volumes
277
e. Exports or shares: This lists the directories that are shared. See Figure 6-75.
Figure 6-75 Export information
f. Monitored Directories: To view a report on a directory that you are monitoring, expand the Monitored Directories node on the Navigation tree and click the directory for which you want to see details (see Figure 6-76).
Figure 6-76 Monitored Directories information
By OS type
Computers are grouped into operating system type. The following operating systems types are available: Windows NT Windows Microsoft Virtual Server Solaris Linux
278
Hewlett-Packard UNIX AIX NetWare Network Appliance Other NAS IBM SAN file system Unknown To get assets for one of the Linux machines, do the following: 1. Select Data Manager Reporting Assets By OS Type. 2. The list of OS types displays. We selected Windows by clicking it to view the list of Windows machines in the environment, as shown in Figure 6-77. Note that the computer can be expanded to show additional information, such as Controllers, Disks, Filesystems, Exports or Shares, and Monitored Directories.
Figure 6-77 OS reports
279
3. Click one of the machines to get information about the computer that has a Windows operating system running, as shown in Figure 6-78.
Figure 6-78 Detailed operating system information
280
By storage subsystem
This lists the available storage subsystems in the environment. For example, you can view the following information (see Figure 6-79): For an ESS subsystem, you can view disk groups, volume spaces, disks, and LUNs. For a SAN Volume Controller, you can view managed disk groups, managed disks, and virtual disks. For IBM FAStT and HP StorageWorks, you can see storage pools, disks, and LUNs. For Hitachi Data Systems, you can see storage pools and LUNs.
Figure 6-79 Asset by Storage Subsystems
281
System-wide
This 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 6-80.
Figure 6-80 Asset System-wide subnodes
Agents
To get the report for agents, use the following steps: 1. Select Data Manager Reporting Assets System Wide Agents. 2. The Report Generation window appears. 3. Select the columns that you want included/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, Connection Errors, and CPU Architecture (see Figure 6-81 on page 283).
282
Figure 6-81 Agent reports
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. 2. The Report Generation window appears. 3. Select the columns that you want included/excluded and click Generate Report. TotalStorage Productivity Center for Data shows you all of the computers, as shown in Figure 6-82. .
Figure 6-82 Computer detailed report
283
4. 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. 2. The Report Generation window appears. 3. Select the columns that you want included/excluded and click Generate Report. 4. 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 (see Figure 6-83 on page 285).
284
Figure 6-83 Disk reports
6.4.3 Availability
TotalStorage Productivity Center for Data can keep track of all agents that are registered. Uptime and statistics regarding sending and receiving signals are saved and can be seen as a report. Two subcategories are available: Ping and Computer Uptime. To get a ping statistic for one of the machines, follow these steps: 1. Select Data Manager Reporting Availability Ping. 2. Five subcategories can be selected: a. By Cluster b. By Computer c. By Computer Group d. By Domain e. Network-wide
285
3. For example, click By Computer. See Figure 6-84. The Selection window appears. 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 computers in the environment. 4. Click Generate Report.
Figure 6-84 Ping by computer
To get a Computer Uptime report for one of the machines, do the following: 1. Select Data Manager Reporting Availability Computer Uptime. 2. Five subcategories can be selected: a. By Cluster b. By Computer c. By Computer Group d. By Domain e. Network-wide 3. For example, click By Computer. See Figure 6-85 on page 287. 4. Click Generate Report. 5. The report displays the availability of the computer and how many times it has been booted.
286
Figure 6-85 Computer Uptime report
6.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.
287
4. One line displays for Network-wide. Click the pie-chart icon to view the report in chart format, as shown in Figure 6-86.
Figure 6-86 Disk capacity reports
5. To focus on the disk capacity for each computer, click the Network-wide tab and click the magnifying glass located to the left of the line. The Disk Capacity report for all of the computers displays, as shown in Figure 6-87.
Figure 6-87 Disk Capacity report
6. To get details for an individual row, click the magnifying glass icon to the left of the row.
288
7. You can select more detail about the disk in the selected computer. TotalStorage Productivity Center for Data creates the same report as found under Data Manager Reporting Asset By Computer Computer name Disks. 8. You can right-click and select Chart: All rows, as shown in Figure 6-88.
Figure 6-88 Chart Disk Capacity
9. The line graph to chart all of the disk capacity by computer is shown in Figure 6-89.
Figure 6-89 Disk capacity by computers
289
To get Network-wide file system capacity, follow these steps: 1. Select Data Manager Reporting Capacity Filesystem Capacity. 2. Click Network-wide. 3. The Report generation window appears. 4. Click Generate Report to create the report for Network-wide. 5. 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 6. Click the magnifying glass icon to see all of the computers in the environment. 7. Right-click and select Chart space usage for all. 8. You get a report of Used Space and Free Space of two computers at a time. 9. Right-click and select Customize this chart to change the chart type or the number of computers at a time, as shown in Figure 6-90 on page 291.
290
Figure 6-90 Filesystem capacity report
A historical report can be important for you to predict the future of capacity depending on current trends. To get a history report, do the following: 1. Select Data Manager Reporting Capacity Filesystem Used Space. 2. Click By Computer. 3. The Report generation window appears. 4. Click the magnifying glass icon next to one of the computers.
291
5. Right-click and select History Chart: Space Used for selected. The chart shown in Figure 6-91 displays, starting from the first scan to the last scan.
Figure 6-91 Space Used historical report
6.4.5 Usage
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. The list and the graphic in Figure 6-92 on page 293 give you an idea of what is possible with Usage Reporting: Access Load Files Directories Users OS User Groups
292
Figure 6-92 The major categories in Usage Reporting
You have already seen several reports at 6.2.1, Predefined reports under the My Reports node on page 222. In this section, you can find several reports that were not mentioned in the My Reports section. To get a Creation Time report, do the following: 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 which were created in: Less than 1 day Within 1 week Within 1 month Between 1 and 2 months Within 1 year More than 1 year
293
6. Click the pie chart icon to view the report in pie chart format, as shown in Figure 6-93.
Figure 6-93 Creation Time report
The File types report is a new feature in TotalStorage Productivity Center for Data. You can view the number of files and their occupied space on the basis of file types. To get a File Types report, do the following: 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 file types within all computers. 6. To select specific file types, click Selection. 7. File types appear in a pop-up window. Put a check mark on the file types that you want to include in the report (for example, check only the following file types: avi, bmp, db2, db, doc, jpg, lwp, and xls.) 8. The report shows the number of files, Type Description, Total Size of the file, and percentage of used space (see Figure 6-94 on page 295).
294
Figure 6-94 File type network-wide
9. Click the magnifying glass icon to the left of the line to display the computers that have selected file types, for example, computers that have *.jpg files. Figure 6-95 should display.
Figure 6-95 Detailed file type by computer
To get a Duplicate File report, do the following: 1. Select Data Manager Reporting Usage Files Duplicate Files. 2. Click By computer. 3. The Report generation window appears. 4. To select the computer, click Selection. Select only one computer.
295
5. This lists duplicate files for the selected computer (see Figure 6-96).
Figure 6-96 Duplicate file report
6. Click the magnifying glass icon to get details of a selected file (see Figure 6-97).
Figure 6-97 Detailed duplicate file report
7. You can automatically trigger Tivoli Storage Manager backup and then delete the file if you want. To do that in the duplicate file list window at Step 5, highlight the file, right-click, and select Create a new archive/backup job.
296
6.4.6 Usage violations

When you set up quotas or constraints in Policy Management, TotalStorage Productivity Center for Data starts to check the usage against quotas and constraints.
6.4.7 Backup
Backup reporting allows us to see the files that are at the most 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 to avoid a problem if something happens. 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.
297
5. The file list displays. It is sorted by Modification Time, as shown in Figure 6-98.
Figure 6-98 Most At Risk files
6. Select a file or files from the list, and right-click. 7. Select Create a new archive/backup or Add an existing archive/backup job. 8. The Create File Archive/Backup Action window appears. Select the backup type, such as Archive, Selective backup, or Incremental backup.
Figure 6-99 Backup options
298
9. Click the When to Run tab to schedule the backup job. 10.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/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. To get 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. 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 and the total number of files to back up, as shown in Figure 6-100.
Figure 6-100 Backup requirements
299
6. You can click the magnifying glass icon to display a report for each computer, as shown in Figure 6-101.
Figure 6-101 Detailed backup storage requirements
7. You can click the magnifying glass icon again to get the file system list in each computer, as shown in Figure 6-102.
Figure 6-102 Detailed backup storage requirements by file system
300
Chapter 7.
Troubleshooting
This chapter provides information about troubleshooting and how to manage errors. In this chapter, we discuss following topics: Log files Configuration files Audit logs Diagnosing IBM TotalStorage Productivity Center problems Troubleshooting CIM Agents and discovery Troubleshooting tpctool Troubleshooting discovery Troubleshooting IBM TotalStorage Productivity Center for Data Problem descriptions and solutions
301
7.1 Log files

There are several product log files to check when you have a problem. See Table 7-1.
Table 7-1 Default log file locations for IBM TotalStorage Productivity Center components Component Data Server Log file location For Windows: c:\Program Files\IBM\TPC\data\log For UNIX or Linux: /<usr or opt>/IBM/TPC/data/log For the Data Server, check the following log files: server_<xxxxx>.log Device Server For Windows: c:\Program Files\IBM\TPC\device\log For UNIX or Linux: /<usr or opt>/IBM/TPC/device/log For the Device Server, check the following log files: "msgTPCDeviceServer.log - the main log file "traceTPCDeviceServer.log - the main trace file "msg.discovery.<individual_log_files> - individual log files from various discovery jogs "msg.control.* - control job log files "dmSvcTrace.log - Disk Manager trace file "tracePerfMgr<xx>.log - Performance Manager trace file Also look in the WebSphere logs for the Device Server. Look in this directory: <TPC_install_dir>\device\apps\was\logs\server1 Common agent For Windows: c:\Program Files\IBM\TPC\ca\logs For UNIX or Linux: /<usr or opt>/IBM/TPC/ca/logs Data agent For Windows: c:\Program Files\IBM\TPC\ca\subagents\TPC\Data\log For UNIX or Linux: /<usr or opt>/IBM/TPC/ca/subagents/TPC/Data/log Fabric agent For Windows: c:\Program Files\IBM\TPC\ca\subagents\TPC\Fabric\log For UNIX or Linux: /<usr or opt>/IBM/TPC/ca/subagents/TPC/Fabric/log GUI For Windows: c:\Program Files\IBM\TPC\gui\log For UNIX or Linux: /<usr or opt>/IBM/TPC/gui/log
302
Component Database schema
Log file location For Windows: c:\Program Files\IBM\TPC\dbschema\log For UNIX or Linux: /<usr or opt>/IBM/TPC/dbschema/log
If you are having problems with the DS4000, DS6000, or DS8000 CIM Agent, you can run a script to collect log information. Go to this directory: Windows: C:\Program Files\IBM\cimagent\cimom Linux: /opt/IBM/cimagent/cimom For Windows, run the following command: run collectLogs.bat For Linux, run the following command: run collectLogs.sh. The script generates a collectedLogs.zip file. Keep in mind that this file will be overwritten if the script is run again. If you are having problems with the SVC CIM Agent, you can run a script to collect log information. Go to this directory: Windows: C:\Program Files\IBM\svcconsole\support For Windows, run the following command: run collectLogs.bat. The script generates a collectedLogs.zip file. Keep in mind that this file will be overwritten if the script is run again.
Chapter 7. Troubleshooting
303
7.2 Configuration files

The default file locations for the configuration files are shown in Table 7-2.
Table 7-2 Default file locations for IBM TotalStorage Productivity Center configuration files Component IBM TotalStorage Productivity Center Data Server Default file location For Windows: c:\Program Files\IBM\TPC\config For UNIX or Linux: /<usr or opt>/IBM/TPC/config For Windows: c:\Program Files\IBM\TPC\data\config For UNIX or Linux: /<usr or opt>/IBM/TPC/data/config Device Server For Windows: c:\Program Files\IBM\TPC\device\conf For UNIX or Linux: /<usr or opt>/IBM/TPC/device/conf Common agent For Windows: c:\Program Files\IBM\TPC\ca\config For UNIX or Linux: /<usr or opt>/IBM/TPC/ca/config Data agent For Windows: c:\Program Files\IBM\TPC\ca\subagents\TPC\Data\config For UNIX or Linux: /<usr or opt>/IBM/TPC/ca/subagents/TPC/Data/config Fabric agent For Windows: c:\Program Files\IBM\TPC\ca\subagents\TPC\Fabric\conf For UNIX or Linux: /<usr or opt>/IBM/TPC/ca/subagents/TPC/Fabric/conf
7.3 Audit logs

IBM TotalStorage Productivity Center has two audit logs. The audit logs provide an audit log for all administrator activities, including identification of users initiating actions. The logs are as follows: Data Server audit log, which is initiated by the GUI. Device Server audit log, which is initiated by the API or CLI.
304
Audit logging is performed at the point of entry: GUI commands are logged in the Data Server audit log. API and CLI commands are logged in the Device Server audit log. Communication between the services are not logged: Data Server to Device Server Data Server to agents Device Server to agents The Data Server audit log is in the following directory: <TPC_install_dir>\IBM\TPC\data\log\AuditTrace.log The Device Server audit log is in the following directory: <TPC_install_dir>\IBM\TPC\device\log\auditTPCDeviceServer.log The Device Server audit log includes the following information: Time stamp User ID IP address of client Service and operation performed Key input and output parameters
7.4 Diagnosing IBM TotalStorage Productivity Center problems

When a problem occurs with IBM TotalStorage Productivity Center, you should collect information to help diagnose the problem. The following sections help you gather the information you need.
7.4.1 General information

When a problem occurs with IBM TotalStorage Productivity Center, you should gather the following information: An exact description of the problem. The function being used. The sequence of steps that resulted in the problem. The expected results from the failing step. Any error messages that you see.
305
The date and time when the problem occurred. The log files collected with the service utility. ESS microcode level or SAN Volume Controller version, if known. The microcode level can be obtained by looking at the properties of the discovered device. ESS, SVC, DS4000, DS6000, or DS8000 CIM Agent version, if known. The last time that inventory collection was performed (this indicates that the repository is in synchronization with the real configuration). Whether the error is repeatable or it occurs intermittently. The answers to the following connectivity questions help you determine whether there is a communication issue between IBM TotalStorage Productivity Center and the CIM Agent server: Is there any firewall enabled interfering with the communication between the IBM TotalStorage Productivity Center components and the CIM Agents? Is it possible to ping the CIM Agents? Is it possible to telnet to the CIM Agents? Is it possible to contact the CIM Agents with a CIM browser? Are the CIM Agents locate in the local subnet with IBM TotalStorage Productivity Center or is a DA in another subnet used for discovery? Is the DA on the remote subnet registered with IBM TotalStorage Productivity Center? Was the CIM Agents SLP registration successful? Use the slptool findsrvs command.
7.5 Troubleshooting CIM Agents and discovery

CIM Agent management is a Disk Service capability. If you are having problems with adding or editing the CIM Agent, check the following: Look in the trace log for errors: <TPC_install_directory>\device\log\dmSvcTrace.log Look for HWN09999 error codes. The database only knows about the last status as updated by the Device Server (through a discovery or probe). If the Device Server is down, the status will not change. The add, edit, or test function only works if the Device Server is up. If
306
you test the CIM Agent, this will update the status. Testing the CIM Agent will not automatically refresh the navigation tree.
7.6 Troubleshooting tpctool

The tpctool is a stand-alone Java client and connects to the Device Server only. The tpctool connects through TCP, HTTP, and SOAP to the Web service APIs. The commands provide query, control, and reporting capabilities only. The commands do not initiate discovery, probes, or configuration and control of agents. The tpctool is installed in the following default directories: C:\Program Files\IBM\TPC\cli (for Windows) /<usr or opt>/IBM/TPC/cli (for UNIX or Linux) The Windows command to run the tool is tpctool. The UNIX or Linux command to run the tool is tpctool.sh. There are two distinct kinds of authentication: User authentication Super user or host-based authentication The user authentication requires a user ID and password authenticated in the Device Server's authentication domain. Role-based authorization is enforced on a per command basis. The super user or host authentication is for the user ID tpc_superuser. The password for this user ID bypasses role-based authorization. This is the required authentication method for AIX-based Device Servers. Some of the control commands run a long time. An example is the mkvol command. There is no way to determine the intermediate status of the command. If the tpctool client stops (for example, the user presses Ctrl-C or the node crashes), all connections with the job is lost. There is no way to reconnect to the host to check on the status. The Device Server logs and trace files (assuming that tracing is on) are shown below. For the Disk commands, see this log: DiskManagerService: dmSVCTrace.log
307
For the Fabric commands, see these logs for the Fabric Manager Service: TPCZoneControl.log msgTPCDeviceServer.log traceTPCDeviceServer.log For the reporting commands, see this log: PerformanceService: tracePerfMgr.log For fabric reports, the commands pass through the Fabric service for authorization. For subsystem reports, the commands pass through the Disk service for authorization. For configuration commands, see this log: ConfigService: traceTPCDeviceServer.log For all other commands, see this log: msgTPCDeviceServer.log Some notes about passwords: You can use the GUI to change the Device Server host authentication password. If the GUI is used to change the password, the password will be updated in the database and the Device Server will be notified. The configuration file for all the Fabric agents need to be manually changed.
7.6.1 Common user errors

Some of the common user problems are: Do not know where the installation directory is. Is the installation directory in a nonstandard location? Did not set the PATH or chdir to the <TPC_install_dir>/cli directory. Using tpctool on UNIX or Linux instead of tpctool.sh. Did not provide the following parameters in the command: -url -user -pwd
308
This is a common error message for tpctool: AAJ000009E Error communicating to the App server. This same error message indicates an invalid port, invalid host, or the Device Server is unreachable. To distinguish what the problem is, you can set a debug flag that prints the Java stack if an exception occurs. Most errors are propagated to tpctool as exceptions. To set this flag: For Windows: set TPCCLIDBG=1 For UNIX or Linux: export TPCCLIDBG=1 For an invalid host, the host name is embedded in the message. For example: [SOAPException: faultCode=SOAP-ENV:Client: msg=Error opening socket: java.net.UnknownHostException:badhost:...] For a valid host, but an invalid port or when the Device Server is down, an example of a message is as follows: [SOAPException: faultCode=SOAP-ENV:Client: msg=Error opening socket: java.net.ConnectException: Connection refused:...] An invalid port is the most common problem. If the Device Server node is unreachable, an example of the message is as follows: [SOAPException: faultCode=SOAP-ENV:Client: msg=Error opening socket: java.net.SocketException: Operation timed out: connect:could be due to invalid address:...]
7.6.2 srmcp commands

Here are some simple srmcp commands for SANEventCorrelatorFactory for fabric: To list the configured filters: "cd <TPC_install_dir>\device\bin\w32-ix86 "srmcp -u <user_ID> -p <password> SANEventCorrelatorFactory list To add a filter with the specified values (any or all can be specified). You can specify just the enterprise, the OIDs, or a combination. cd <TPC_install_dir>\device\bin\w32-ix86 srmcp -u <user_ID> -p <password> SANEventCorrelatorFactory add filter [enterprise=<enterprise>][genericTrap=<number>] [specificTrap=<number>][<OID>=<value>]
309
To specify an IP address that will be filtered for the specified filter: cd <TPC_install_dir>\device\bin\w32-ix86 srmcp -u <user_ID> -p <password> SANEventCorrelatorFactory add address <ID> <IP_address> To remove a specified filter: "cd <TPC_install_dir>\device\bin\w32-ix86 "srmcp -u <user_ID> -p <password> SANEventCorrelatorFactory remove filter <ID> To remove the IP address from the filter list: "cd <TPC_install_dir>\device\bin\w32-ix86 "srmcp -u <user_ID> -p <password> SANEventCorrelatorFactory remove address <ID> <IP_address> Here is the srmcp command to change the host authentication password: cd <TPC_install_dir>\device\bin\w32-ix86 srmcp -u <user_ID> -p <password> ConfigService setAuthenticationPw <new_host_password> Here is the srmcp command to change the DB2 password (not the db2admin password) that the server uses: cd <TPC_install_dir>\device\bin\w32-ix86 srmcp -u <user_ID> -p <password> ConfigService setPw <new_host_password>
7.7 Troubleshooting discovery

For discovery problems, there are several service level logs to check: msgTPCDeviceServer.log traceTPCDeviceServer.log dmSvcTrace.log tracePerfMgr.log TPCZoneControl.log These logs are located in this directory: <TPC_install_dir>\IBM\TPC\device\log You can get a core dump file in this directory: <TPC_install_directory>\device\apps\was
310
For Windows, follow these steps: 1. Go to this directory: C:\Program Files\IBM\TPC\device\apps\was\bin 2. Enter the following: wsadmin set jvm [$AdminControl completeObjectName type=JVM,process=server1,*] $AdminControl invoke $jvm dumpThreads For AIX or Linux, follow these steps: 1. Enter this command: ps -ef | grep "IBM/TPC" | grep "apps/was" | awk '{print $2}' | xargs kill -3 To discover the job activity, issue the following command: srmcp -u <user_ID> -p <password> DiscoverService list jobs To determine the DB2 activity, issue the following DB2 commands: db2 db2 db2 db2 list applications show detail > dbListApplicationDetails.out update monitor switches using statement on lock on table on uow on connect to tpcdb get snapshot for all on tpcdb > dbsnap.out
7.7.1 Common user errors

A discovery or probe operation does not complete. This can be caused by the following: There is a lock contention when IBM TotalStorage Productivity Center accesses the database tables. DB2 does not return information from a query. The CIM Agent starts returning information and then stops. To work around this problem, stop and then restart the Data Server and Device Server. Also, collect log information using the service tool.
311
7.8 Troubleshooting IBM TotalStorage Productivity Center for Data

To troubleshoot IBM TotalStorage Productivity Center for Data problems, follow these steps: Turn logging and tracing on through the GUI. Remember to turn tracing off when you are finished. Use the service tool to get the Device Server and Data Server logs and the common agent. Run repocopy to get a copy of the database. Get the DB2 logs: Db2diag.log Get output from the db2 list applications command: db2 connect to tpcdb db2 list applications
7.8.1 Hints and tips

Here are some hints and tips: The JVM heap sizes should be as follows: Data Server: 1 GB. Device Server: 1.5 GB. GUI: 512 MB. DB2 also uses 512 MB to 1 GB of memory.
On UNIX, the swap space should be more than physical memory on the machine. It would be good if the swap space is twice the amount of physical memory. It is better to run the GUI on a different machine. After you import repocopy data from a customer, you will have to change the Device Server host authentication password in t_res_server table. There will be at least two entries in that table. The entry with server_id 1 is the Device Server entry. You need to copy the host authentication password from the following file: <TPC_install_directory>\device\conf\setup.properties If you are importing data from UNIX to Windows or from Windows to UNIX, you will need to change the t_res_auth_roles table. Change the value of the group_name column to the group name that your logon user ID belongs to.
312
To change the database logon password, follow these steps: a. Go to a command prompt window and go to the following file: <TPC_install_directory>\data\config\repository.config b. Run the following command: <TPC_install_directory>\jre\bin\java -classpath <TPC_install_directory>\data\server\lib\TSRMsrv.zip com.tivoli.itsrm.repository.Transform -p <new_db2admin_password> repository.config c. Stop and restart the Data Server. Logging and tracing can be turned on through the GUI. It will be turned on until you turn it off through the GUI. After data migration from IBM TotalStorage Productivity Center V2.x to IBM TotalStorage Productivity Center V3.1, note the following: Reports will work. New functions like volume creations, performance monitoring, fabric-related functions will not work. For the new functions to work, the subsystem probes need to be run. The subsystem probes will not work until a CIM Agent discovery job is performed. Data agent upgrade options: For IBM TotalStorage Productivity Center V2.x installation program, there were two options available: scheduled upgrades of agents or upgrade of agents right after the server is upgraded. That option is no longer available. All the Data agent upgrades need to be scheduled. To turn off the scheduling update option and to force the agent upgrades right away, after data migration, delete this file: <TPC_install_directory>\data\server\SCHEDULED_UPGRADES Stop and restart the Data Server.
313
7.9 Problem descriptions and solutions

This section describes problems that you might encounter and the solutions for those problems This section includes the following categories: Installation problems Reporting and GUI problems Switch problems Miscellaneous problems
7.9.1 Installation problems

This sections discusses common installations problems and their solutions.
Problem: The file system storing the database tablespaces runs out of space
The file system storing the database tablespaces runs out of space. This is shown by the following kinds of errors, as seen in the DB2 log called db2diag.log: 2005-11-06-12.59.10.815891-420 E36562387C690 LEVEL: Error PID : 176316 TID : 1 PROC : db2pclnr 0 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:0 MESSAGE : ADM6017E The tablespace "TPCTBSPTEMP" (ID "5") is full. Detected on container "/home/db2inst1/db2inst1/TPCDB/TPC/TPCTBSPTEMP" (ID "0"). The underlying file system is full or the maximum allowed space usage for the file system has been reached. It is also possible that there are user limits in place with respect to maximum file size and these limits have been reached. This problem is seen on AIX 5L V5.x with a JFS file system. Large files need to be enabled on the file system because the tablespace files can get quite large. Enable large files on JFS or JFS2.
314
Solution
During installation of AIX 5L V5.1 or later, ensure that JFS or JFS2 with large file system support is installed. Read the AIX documentation to learn how to back up and restore data between file systems. We recommend ensuring that the file system size (especially for /home) is not too small (for example, not less than 4 GB). Back up your existing data before you recreate your file system. For information about file systems, see: http://publib.boulder.ibm.com/infocenter/pseries/index.jsp?topic=/com.i bm.aix.doc/aixbman/admnconc/fs_types.htm
Problem: Get message "Specified directory is not empty" when installing common agent
This condition can occur when you uninstall and reinstall the common agent.
Solution
If you get this message, ensure that the ca and log directories are empty. For example, if you used the default directory, check the following directory: C:\Program Files\IBM\TPC (for Windows) /opt/IBM/TPC (for UNIX or Linux)
Problem: Upgrading from IBM TotalStorage Productivity Center for Data 2.x to IBM TotalStorage Productivity Center V3.1 (database), the topology view does not display the L2 view
When you upgrade from IBM TotalStorage Productivity Center for Data V2.x to IBM TotalStorage Productivity Center V3.1 (database), the topology view does not display the L2 view. This problem occurs because some of the database configuration parameters do not become effective until a connection reset.
Solution
To work around this problem, follow these steps: 1. Stop the Device Server and Data Server. 2. Start the Device Server and Data Server.
Problem: Unable to uninstall the common agent

An upgrade of the common agent to Version 1.2.2 does not modify the scripts used to start the common agent. Run the following commands to create the additional startup scripts.
315
Solution
Run the following command to create the additional startup scripts: AIX ln -s <common_agent_install_dir>/endpoint.sh /etc/rc.d/rc2.d/ K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh /etc/rc.d/rc2.d/ S71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh /etc/rc.d/rc3.d/ S71itca<agent_ID> Solaris ln -s <common_agent_install_dir>/endpoint.sh K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> HP-UX ln -s <common_agent_install_dir>/endpoint.sh K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> Linux ln -s <common_agent_install_dir>/endpoint.sh K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh K71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> ln -s <common_agent_install_dir>/endpoint.sh S71itca<agent_ID> /etc/rc.d/rc0.d/ /etc/rc.d/rc1.d/ /etc/rc.d/rc2.d/ /etc/rc.d/rc3.d/ /etc/rc.d/rc5.d/ /sbin/rc0.d/ /sbin/rc1.d/ /sbin/rc2.d/ /sbin/rc3.d/ /etc/rc0.d/ /etc/rc1.d/ /etc/rc2.d/ /etc/rc3.d/
316
Where <common_agent_install_dir> is where the common agent is installed and <agent_ID> is the installed instance. (If only one agent is installed on the computer, then the value will be "0".) The value of <agent_ID> is from the ep.reg file. The <agent_ID> is the first entry in the pipe delimited list. For example, see the following ep.reg file: # cat /opt/tivoli/ep.reg <agent_ID> | agent | /opt/tivoli/ep | 1.2.2.8 | 0 | 1.4.2 | IBM Corporation | root | 1/16/06 3:21 PM | The ep.reg file is found in the following directories: Windows: c:\Program files\tivoli\ep.reg UNIX or Linux: /opt/tivoli/ep.reg
Problem: The IBM TotalStorage Productivity Center agent uninstallation program reports that it has failed on the command: uninstall.sh "false"
Solution
This problem can be ignored if it was caused by the common agent uninstallation program failing to delete missing startup scripts. If this was the cause, the common agent uninstall.log file will contain entries like this: Agent, com.tivoli.agent.install.Service, dbg, Utility.executeCommand (sh -c rm -r /etc/rc.d/rc0.d/K71itca0) returned 1
Problem: Get error message "migrationUtility.jar file not found."

If you are trying to run the migration utility, this message will be displayed.
Solution
See the IBM TotalStorage Productivity Center Flash for current information about how to run the migration utility. The Web site for the Flash is: http://www.ibm.com/servers/storage/support/software/tpc
317
Problem: Installing a remote agent fails

You are getting a connection error to the remote computer when you try to install a remote agent.
Solution
When you are installing a remote agent from a Windows computer, you must have the HOSTS file set properly on the Windows computer. For information about changing the HOSTS file, see Appendix F, Hints and Tips", in the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774.
Problem: Agent registration fails when you are running AIX with IPv6
Solution
To work around this problem, follow these steps: 1. First, install the common agent with a flag set. Use the agent CD or go to the directory where you have the common agent installation program and run the setup.sh program: <common_agent_install_dir>/commonagent/setup.sh -W beanArguments.agentJVMParms="-Djava.net.preferIPv4Stack=true" 2. Use the IBM TotalStorage Productivity Center installation program to upgrade the Data agent or Fabric agent.
Problem: You get error message "PM INS3105E: Host <fully_qualified_host name> is associated with an invalid loopback IP 127.0.0.1"
You get the error message above when you have a UNIX or Linux computer and are trying to install a remote agent.
Solution
In the /etc/hosts file, the line for the specified IP address should be: 127.0.0.1 and not 127.0.0.1 <fully_qualified_host name> <short_host name> localhost.localdomain localhost You should have a separate entry for the regular IP address and host name of the IBM TotalStorage Productivity Center server. For example: 9.47.98.63 <fully_qualified_host name> <short_host name> localhost.localdomain localhost
318
Problem: You cannot upgrade an HP-UX V2.x Data agent using the IBM TotalStorage Productivity Center installation program
Solution
To work around this problem, follow these steps: 1. First, upgrade the common agent. Use the agent CD or go to the directory where you have the common agent installation program and run the setup.sh program: <common_agent_install_dir>/commonagent/setup.sh 2. Use the IBM TotalStorage Productivity Center installation program to upgrade the Data agent.
Problem: Get error message "INS3078E: Miniprobe failed on remote computer xxx.xxx.xxx.xxx, error x.
When you are installing a remote Data agent, you get this message in the error log.
Solution
Check to make sure that you are not using multiple NIC cards. Multiple NIC cards are not supported. On a computer that has two NIC cards, the installation program returns the wrong IP address for the miniprobe results. On a computer that has two NIC cards, the installation program gets the address of the first NIC card, and uses that. If the agent is addressed from the second NIC card, the address it received to return the information to is incorrect, and the socket call fails.
Problem: Data Server crashes on AIX

The Data Server crashes on AIX with the following messages in the system error logs: ERROR LOGGING BUFFER OVERFLOW caused by EXCESSIVE LOGGING BY SOFTWARE PROGRAM.
Solution
Increase the paging space on the server.
319
7.9.2 Reporting and GUI problems

This section discusses common reporting and GUI problems and solutions for them.
Problem: IBM TotalStorage Productivity Center could crash when canceling Disk Manager reports
When you display Disk Manager reports in the GUI: Disk Manager Reporting Storage Subsystem Performance By Volume For this condition to occur, you have run Performance Manager on the subsystem and have a lot of data. When you try to run this report, then cancel the report (red circle X on the upper left side), this could cause IBM TotalStorage Productivity Center to crash. This condition is dependent on the machine resources, what the user has set the JVM heap size to, and the number of volumes and switches the user is collecting performance data on.
Solution
Do not cancel this report.
Problem: Window displays "No saved IP addresses could be found."

If no base IP addresses have been specified for the SNMP address scan in the out-of-band Fabric discovery options, you will see this pop-up window when you run an out-of-band Fabric discovery job.
Solution
The pop-up window asks "Do you wish to continue with this discovery?" Click Yes to continue. This will run discovery for any IP addresses in the out-of-band Fabric agent list.
Problem: Reports which generate a lot of data can crash the tpctool CLI with Java(TM) out of memory errors
Solution
To work around this problem, reduce the report size by requesting less information. For example, rather than specifying all columns for a report, you can specify fewer columns for the report.
320
Problem: The Volume Performance Advisor wizard does not show a list of available hosts attachments for an ESS
Solution
Check to see if a Fabric agent has been installed on a host machine attached to the ESS. An in-band fabric scan must be run before IBM TotalStorage Productivity Center can discover the hosts that are currently connected to the subsystem. The in-band scan allows IBM TotalStorage Productivity Center to detect that host's connectivity to the ESS. If IBM TotalStorage Productivity Center is unsure that a host is connected, even if defined in the subsystem configuration, that host is not displayed on the Volume Performance Advisor window for selection.
Problem: Unsuccessful probe

When you attempt to launch either the Create Volumes or Create Virtual Disk wizard (depending on the device type) for a device that has not had a successful probe, you will see this error message: HWN020002E Mandatory parameter PortIDs missing When you click OK on the error dialog, you cannot proceed with the Create wizard because the information gathered by the probe is needed to populate the widgets in the wizard.
Solution
You must cancel out of the Create wizard, then create and schedule a probe for the device or devices. When the probe completes successfully, then you will be able to launch the Create Volumes or Create Virtual Disks wizard. If the probe fails, you will not be able to create the volumes or VDisks.
7.9.3 Switch problems

This section discusses switch problems and their solutions.
Problem: McDATA switch domain number

The McDATA switch domain number in the IBM TotalStorage Productivity Center GUI should be consistent with what the switch software is displaying, but is not.
Solution
If you are using a McDATA switch, the domain ID displayed by IBM TotalStorage Productivity Center has a different value from the one displayed by McDATA's management application. IBM TotalStorage Productivity Center displays the domain ID on the Properties dialog for a selected switch or on the Zone dialog for zone control. The reason for this difference for the domain ID is because the IBM
321
TotalStorage Productivity Center API call to the McDATA switch has some additional encoded information in the high-order bits. For example, a McDATA switch with the domain ID of 1 (as displayed on McDATA's management application) is displayed as 97 (hexadecimal 61, where the 6 represents the high-order bit encoding information).
Problem: Editing switch or subsystem alerts causes old devices to appear in list of selected devices
If you create a switch or subsystem alert using a Performance Manager trigger condition, then save, edit, and reopen the alert, this can cause the old device to reappear in the list of selected devices.
Solution
You can avoid this problem by not editing alerts to change trigger conditions or devices. Just delete the old alert you do not want and create a new one.
Problem: On Create Switch Alerts window, Switches tab, the list of switches shows duplicate entries
On the Create Switch Alerts window, Switches tab, the list of switches shows duplicate entries. The list of switches in the Create Switch Alerts window are listed by the display name. However, if the display name is null, the logical name is used instead. If you have multiple switches with duplicate display names or duplicate logical names (if the display names are null), you will see duplicate entries in this window.
Solution
Ensure that you have unique display names and logical names for your switches.
Problem: Get error message "GEN7046E=The device ID [{0}] is not available for use with alert condition {1}."
If you create a switch or subsystem alert using a Performance Manager trigger condition, then save it and change the trigger by editing it, this can cause the message GEN7046E to be displayed.
Solution
You can avoid this problem by not editing alerts to change trigger conditions or devices. Just delete the old alert you do not want and create a new one.
322
7.9.4 Miscellaneous problems

This section discusses miscellaneous problems and solutions for them.
Problem: Korean language environment

You will not be able to view the log files from the IBM TotalStorage Productivity Center GUI because of a DB2 JDBC driver problem.
Solution
You will have to read the files using another text viewer like Notepad.
Problem: Cannot collect logs from the service tool

Solution
When you install a remote Data agent or Fabric agent and want to collect service logs for them, you must run the service tool from the remote agent machine from this directory: <common_agent_install_dir>\subagents\TPC\service For example, if you used the default directory on UNIX or Linux, the directory path would be: /opt/tivoli/ep/subagents/TPC/service The service tool is installed in several locations, but you should only run the tool from the remote machine directory listed above.
323
324
Appendix A.
Hands-on lab example

This appendix provides an example set of exercises to provide some hands-on experience with TotalStorage Productivity Center for Data V3.1 in a lab environment.
325
Overview
Ask yourself the following questions: What do you really know about your data? Are you sure the data you are storing is strategic and current? Is your best Linux administrator also your biggest MP3 collector? Are the data's owners still with the organization? Is all your data being backed up regularly? Can you identify data at risk? Are users or departments cost-accountable for their use of storage? Until you can understand and manage the data you already have, it will be difficult to forecast future storage needs or to justify purchasing additional storage. You need to ensure that your current storage resources are being managed effectively before you invest in more. This is where IBM TotalStorage Productivity Center for Data will help. It allows you to control your costs by: Predicting your storage requirements accurately Preventing storage downtime Providing usage information Managing more with current staff Expiring data from expensive storage to tape Simplifying Administration This set of exercises lets us understand how TPC for Data can answer these questions.
Getting started with TPC for Data lab exercise

In the following exercises that comprise the lab, we explore some of the basic tools needed to gather data about your environment. These exercises assume you have already installed TPC for Data. The systems shown in these exercises will vary depending on your environment. 1. Getting started with TotalStorage Productivity Center for Data. 2. Run a scan job. 3. Define a Quota. 4. Define a Constraint. The above exercises will help us understand how to navigate within the product. The first exercise leads us through logging onto the system and the initial
326
windows you will encounter. The second exercise explains the mechanics about scanning a system to obtain file level information about the data on that system. The third exercise explores the defining of a quota for storage usage in the environment and generates an alert when a set threshold is exceeded. The last exercise uses constraint processing to generate alerts regarding file types that are not allowed in the storage environment.
Exercise 1: Getting started with TPC for data

1. Sign on to your TPC server using the user ID with the password.
Figure 7-1 Dashboard view after log on
2. The Explorer-like tree appears on the left side of the main window. You can expand, select, and collapse the nodes on this tree to navigate all of the Configuration, Monitoring and Alerting, Policy Management, and Reporting functions of the tool. TPC for Data is divided into the following sections, as shown in Figure 7-2: Data Manager Data Manager for Databases Data Manager for Chargeback
Figure 7-2 TPC for Data tree
The Data Manager mines all data coming from the file system and formats reports to display file system data.
Appendix A. Hands-on lab example
327
The Data Manager for Databases goes into supported databases and formats reports to display information about the databases. The last section, Data Manager for Chargeback, is a simplified charging system to enable you to assign dollar values to totals collected by TPC.
Exercise 2: Run a Scan job

Scans collect statistics on the usage and trending of actual storage consumption. Scan results are stored in the Enterprise Repository and supply the data necessary for Capacity, Usage, Usage Violations, and Backup Reporting facilities. To create a new Scan job: 1. For this exercise, go to the Navigation Tree and select Data Manager Monitoring Scans. Right-click the Scans node. Select Create Scan from the pop-up menu. The Create Scan dialog appears in the content pane. The content pane displays the tabs for defining a scan. The tabs are Filesystems, Directory Groups, Profiles, When to Scan, and Alert tabs. The following is an overview of the functions of the various tabs:
Filesystems tab
The computers and file systems whose storage usage and consumption are to be monitored are selected on the Filesystems tab. As can be seen from the Available list box, scans can be run against individual file systems and computers, or on groups, providing that the groups have already been defined. See Figure A-1 on page 329.
328
Figure A-1 Filesystems tab
2. Highlight the desired file systems, computers, or groups in the Available list box. 3. Click the button to move the selections over into the Current Selections list box. Entries may be removed from the Current Selections list box in the same fashion, using the button on the dialog. For this exercise, expand only the Computers list, select the Kenny computer and move it to the Current Selections column. Note: If a group is added to the Current Selections List Box, but there is a need to exclude individual members of the group, simply add the group per the instructions above, and then right click the member(s) to be excluded from within the Current Selections list box, and select Exclude from the pop-up menu. This will create an Excludes tree in the Current Selections list box.
329
For this exercise, exclude the C: disk from the scan on Kenny by clicking on the + next to Kenny's disks to view all disks associated with Kenny, right click the C: disk under Kenny, and select the C: disk to exclude it. See Figure A-2.
Figure A-2 Create Scan window
Directory Groups tab

Use Directory Groups to group together directories to which you want to apply the same storage management rules. See Figure A-3.
Figure A-3 Directory Groups tab
330
Note: If the desired directory group does not exist, click the New Directory Group button at the bottom of the dialog to create the appropriate group. For this exercise, we do not select any directory groups.
Profiles tab
Profiles control what files are scanned and what statistics are gathered by a Scan job. Use the Profiles tab to select which Profiles to use during the scan of the selected computers and file systems. See Figure A-4
Figure A-4 Profiles tab
Highlight the desired Profile(s) in the Available Profiles list box. Click the button to move the selections over into the Current Selections list box. Entries may be removed from the Current Selections list box in the same fashion, using the button on the dialog. Note: There are two possible selections: Click the top to apply the selected Profile(s) to Filesystems. Click the bottom to apply the selected Profile(s) to Directories.
331
For this exercise, highlight all the default profiles that begin with "TPCUser" and move them to the "Profiles to apply to Filesystems" column. Note: To collect statistics according to TotalStorage Productivity Center for Data default settings, select all of the default Profiles.
When to Run tab

In the When to Run tab, schedule when this job should be run. The following options are available (see Figure A-5): Run Now: To scan immediately after saving the Content panel Run Once At: To schedule a single execution of a Scan at a particular date and time Run Repeatedly: To specify a periodic execution of a Scan based upon a predefined schedule
Figure A-5 Where to Run tab
4. Click the radio buttons next to Run Now, Run Once At, and Run Repeatedly to view the options for each of the selections. For this exercise, select the Run Now option.
332
Note: On the When to Run tab, the time zone for which the job should be run can also be specified. The default will be the time zone in which the TPC-DATA server is located, but it can be adjusted to accommodate scheduling in other time zones.
Alert tab
Use the Alert tab to define an alert that will be triggered if the Scan job fails. See Figure A-6.
Figure A-6 Alert tab
The following describes what you can define within the main sections of the Alert tab: SNMP Trap: Generates an SNMP-based message to a console or terminal. TEC Event: Generates a message to be sent to the Tivoli Enterprise Console. Login Notification: Generates a message to a specified user upon logging on to the system. Windows Event Log: Generates an entry in the Windows Event Log.
333
Run Script: Executes a predefined script. Email: Generates an e-mail message to specified users or groups of users. For this exercise, select Windows Event Log and save the Scan definition, either by selecting File Save from the menu above, or by clicking the diskette icon in the toolbar. Save the scan with a name of "TPCPoTScan". The scan will be submitted when it is saved. To check the status of the scan job expand Data Manager Monitoring Scans administrator.TPCPoTScan. Right-click Administrator.TPCPoTScan and select Refresh Job List. Notice that the date line for the submitted job will change from blue to green when the scan status changes from running to completed. Click the date line for the submitted scan to display the scan summary. Click the magnifying glass to view the scan detail log. Select Window from the action line and select Close all Windows without changes to clean up the display or use Ctrl+D.
Exercise 3: Define a quota

Quotas are used to define limits on the amount of storage that a user or a group of users can consume. The evaluation of a quota is done by aggregating the information that has been collected by all of the various scans, and then checking the quota against the aggregated data. This is done at the TPC DATA server and does not require communication to the TPC DATA agents. Note: Since quota evaluation is done based upon previously gathered Scan information, we recommend that quota analysis be run after all relevant scan jobs have completed. Quotas may be limited at three different levels for a user or group of users: Filesystem: Define quotas for a user or group of users at the file system level. Computer: Define quotas that places limits on a specific machine for a user or group of users. This means that the quota will be enforced on each computer for which the quota is defined. Network: Define quotas that place limits over multiple machines. Network level limits can be placed on users or groups of users for all the computers (or a chosen subset) or file systems in the network.
334
Quotas are broken down into two specific types: User Quota: Select users or group of users for a quota that have been defined within IBM TotalStorage Productivity Center for Data. OS User Group Quota: Select OS User Groups for a quota. OS User Groups are groups of users that have been defined in the operating system outside IBM TotalStorage Productivity Center for Data. To define a network quota: For the exercise, in the TPC DATA Navigation Tree, select Data Manager Policy Management Quotas User Computer. Right-click the Computer Node and select Create Quota from the pop-up window. The content pane displays the four tabs for defining the parameters for the Quota: Users, Computers, When to Run, and Alert. See Figure A-7.
Figure A-7 Create Quota pane
Users tab
Selecting users is the first step in defining a quota. Use the Users tab to select individual users and user groups to which the quota will apply. User groups must have been defined prior to defining the quota.
335
The Profile selection list controls which storage usage statistics are used when checking for quota violations. Since quotas are for use against data that relates to users, only those profiles for which the Summarize usage by owner check box was selected when defining the profile are displayed. Note: Make sure that the selected profile is used in scans of all the file systems chosen on the Filesystems tab. This ensures that the quota is fairly enforced for all users. 1. Expand the User Groups and User nodes, and highlight the desired users or groups in the Available list box. Note: Ctrl-Click or Shift-Click may be used to select ranges of Users or Groups as in any other windows application. 2. Click the button to move your selections over into the Current Selections list box. Entries may be removed from the Current Selections list box in the same fashion, using the button on the dialog. For this exercise, select the User tab, expand User Group and User, select user group TPCUser.Default User Group and the user All Users and move them to the Current Selections box. See Figure A-8.
Figure A-8 Users tab
336
3. Select the Filesystems, Filesystem Groups, Computers, and Computer Groups in the same fashion as on the Users tab above. For this exercise, click the Computers tab, expand Computers, locate All Computers, and move it to the Current Selections box. See Figure A-9.
Figure A-9 Computers tab
4. Click the When to Run tab on the Create Quota dialog.
When to Run tab

In the When to Run tab, schedule when this job should be run. The following options are available: Run Now: To check immediately after saving the Content panel Run Once At: To schedule a single execution of a Check at a particular date and time Run Repeatedly: To specify a periodic execution of a Check based upon a redefined schedule 5. Click the radio buttons next to Run Now, Run Once At, and Run Repeatedly to view the options for each of the selections Note: On the When to Run tab, the time zone for which the job should be run can also be specified. The default will be the time zone in which the TPC DATA server is located, but it can be adjusted to accommodate scheduling in other time zones. For this exercise, select Run Now.
337
6. Click the Alert tab in the Create Quota dialog.
Alert tab
Use the Alert tab to define an alert that will be triggered if the Quota condition is met. The following describes what you can define within the main sections of the Alert tab: When evaluating a quota, the only valid value in the Condition field of the Triggering Condition section is User Consumes More Than. The Value and Value Units field are used to specify the threshold amount of data that, once exceeded, will trigger the alert. For this exercise, enter 5 in the value field and select Megabytes from the drop down. The following actions are available in the Triggered Actions section. These actions will be executed upon completion of a Quota Evaluation when the User Consumes More Than triggering condition has been met. SNMP Trap: Generates an SNMP-based message to a console or terminal. TEC Event: Generates a message to be sent to the Tivoli Enterprise Console. Login Notification: Generates a message to a specified user upon logging in to the system. Windows Event Log: Generates an entry in the Windows Event Log. Select the severity of the event using the Event Type field. Run Script: Executes a predefined script. Email: Generates an e-mail message to specified users or groups of users. 7. For this exercise, select Windows Event Log. Save the Quota definition, either by selecting File Save from the menu above, or by clicking the diskette icon in the toolbar. Save the quota with the name TPCPoTQuota. When the Data Manager Policy Management Quotas User Computer node in the function tree is expanded, a sub node for the quota definition will appear.The name that should appear is administrator.TPCPoTQuota. To check the results of the Quota, expand Data Manager Policy Management Quotas User Computer administrator.TPC PoT Quota. Right-click the administrator.TPC PoT Quota and select Refresh Job List. Notice that the date line for the submitted job will change from blue to green when the job status changes from running to completed. Click the date line for the submitted quota to display the quota check results. Click the magnifying glass to view the quota check detail log.
338
Also, check the Alert Log. To check the results in the Alert Log, expand TotalStorage Productivity Alerting Alert Log All. Click All, which will display all recent alerts that have been generated. Select the magnifying glass next to the alert that has an alert object of USER. This will display the alert for the quota check that was just executed. 8. Select Window from the action line and select Close all Windows without changes to clean up the display.
Exercise 4: Define a Constraint

Constraints define the acceptable and unacceptable file types, file sizes, and file owners for a computer or group of computers. Constraints do such things as restrict users from putting certain files (for example, MP3 files) on monitored servers.
To define a Constraint
1. In the TPC DATA Navigation Tree, select Data Manager Policy Management Constraints. 2. Right-click the Constraint Node and select Create Constraint from the pop-up window.
339
The content pane displays the four tabs for defining the parameters for the Constraint: Filesystems, File Types, Users, Options, and Alert. See Figure A-10.
Figure A-10 Create Constraint pane
Filesystems tab
Selecting file systems and computers to process against is the first step when defining a Constraint. Use the Filesystems tab to select individual file systems and computers, as well as file system and computer groups to which the Constraint will apply. Filesystem and computer groups must have been defined prior to defining the constraint. 3. Click the button to move your selections over into the Current Selections list box. Entries may be removed from the Current Selections list box in the same fashion, using the button on the dialog.
340
For this exercise, select Data Manager Policy Management Constraints. Right-click Constraints and select Create Constraint. Select the Filesystems tab, expand Computers, and select Kenny to move to the Current Selections. Expand Kenny under Current Selections and exclude the C:\ drive from constraint processing by right-clicking the C:\ drive and selecting Exclude. This leaves only the E:\ drive selected for the constraint processing. See Figure A-11.
Figure A-11 Filesystems tab
341
File Types tab

Use the File Types tab to select the file types that will be allowed or forbidden. 4. Select the File Types tab on the Create Constraint Dialog. See Figure A-12.
Figure A-12 File Types tab
5. Click the Forbid file matching these patterns radio button to not allow files of the specified type on a server, or click the Allow ONLY file matching these patterns radio button to allow files only of the specified type on a server. Note: When the Forbid radio button is selected, the title of the right hand list box is Forbidden Files. If the Allow radio button is selected, the title of the right hand list box changes to Allowed Files. 6. Click the file type(s) to be allowed or forbidden in the Choose a file type list box. Several common file types are predefined upon installation, and others can be added on an ad-hoc basis. Click the button to move your selections over into the Allowed Files/Forbidden Files list box. Entries may be removed from the Allowed Files/Forbidden Files list box in the same fashion, using the button on the dialog.
342
Define one or more custom file types to be included in the Constraint by entering a value in the Or enter a pattern field. Press Enter to add the custom defined file type to the Allowed Files/Forbidden Files list box 7. For this exercise, select the File Types tab, use the scroll bar to scroll down to the bottom of the window, and in the Or enter a pattern box enter *.m4a and move this pattern to the Forbidden Files column by pressing Enter. Select the button for Forbid files matching these patterns. See Figure A-12 on page 342
Options tab
Note: There will be no operations in this section. Use the Options tab to define the file characteristics that will trigger the alert. The Options tab consists of the following three sections: Violating File Limits This sets a maximum number of violating files per agent. This option exists to provide the user with controls on the amount of time a scan will take on a particular agent. Alert On Files Use this section to define alerts for files based on characteristics other than file type and file owner. These characteristics include: Files that have not been accessed in a user-defined length of time. Enter a value for the number of days files have not been accessed. Files that are larger than a user-defined size. Enter a value for the file size limit. Files that have the SET-UID root bit "on" (This can be a security consideration). Files that have been modified and not backed up. Enter a value for the number of days files have been modified and not backed up.
343
File Filter Text This section displays a where clause that will be used as a filter for locating files that violate the Constraint definition. The choices you make on this tab and the choices you made on the Users and File Type tabs are reflected in the content of this where clause. To edit the where clause filter text, click the Edit Filter button on the right part of the tab. This will allow you to create new where conditions and groupings using the where clause interface. See Figure A-13.
Figure A-13 Edit Filter
8. If desired, make selections on this dialog.
344
Alert tab
Use the Alert tab to define an alert that will be triggered if the Constraint condition is met. The following describes what you can define within the main sections of the Alert tab: When evaluating a quota, the only valid value in the Condition field of the Triggering Condition section is Violating Files Consume More Than. The Value and Value Units field are used to specify the threshold amount of data that, once exceeded, will trigger the alert. The following actions are available in the Triggered Actions section. These actions will be executed upon completion of a Constraint Evaluation when the Violating Files Consume More Than triggering condition has been met. SNMP Trap: Generates an SNMP-based message to a console or terminal. TEC Event: Generates a message to be sent to the Tivoli Enterprise Console. Login Notification: Generates a message to a specified user upon logging in to the system. Windows Event Log: Generates an entry in the Windows Event Log. Run Script: Executes a predefined script. Email: Generates an e-mail message to specified users or groups of users.
345
9. Click the Alert tab on the Create Constraint dialog. See Figure A-14.
10.Save the Constraint definition, either by selecting File Save from the menu above, or by clicking the icon in the toolbar. When the Data Manager Policy Management Constraint node in the function tree is expanded, a sub node for the constraint definition will appear. For this exercise, enter the Triggering Condition so that files that consume more than 1 KB are identified. Select the box for Windows Event log in the Triggered Actions section. Click the icon in the toolbar and save the constraint with the name TPCPoTConstraint. See Figure A-15 on page 347.
346
11.Run the TPCPoTScan again to collect new constraint data. To rerun scan job, expand Data Manager Monitoring Scans administrator.TPCPoTScan. Right-click the Administrator.TPCPoTScan and select Run Now from the drop-down menu. Click the date line for the submitted scan to display the scan summary. Click the magnifying glass to view the scan detail log. 12.Select Window from the action line and select Close all Windows without changes to clean up the display.
347
348
Appendix B.
Sample questions
This sample test is designed to give the candidate an idea of the content and format of the questions that will be on the certification exam. Performance on the sample test is not an indicator of performance on the certification exam and this should not be considered an assessment tool.
Sample test 900: Questions and answers

1. The customer has DB2 and Oracle databases. The customer's key requirements include host-centric and fabric discovery. Which components of TotalStorage Productivity Center V3.1 (TPC) should be recommended? a. TPC for Data and TPC for Disk. b. TPC for Data and TPC for Fabric. c. TPC for Data and TPC for Replication. d. TPC for Data, TPC for Fabric, and TPC for Disk.
349
2. In a UNIX environment, which two user IDs are required in order to install TotalStorage Productivity Center V3.1 (TPC) agent software and monitor the RDBMS? (Choose two.) a. Root user ID. b. DBA user ID. c. Guest user ID. d. Domain user ID. e. Administrator user ID. 3. TPC V3.1 components use a set of TCP/IP ports for communication. In a secure environment with firewall separation from the TPC Server and TPC agents, what needs to be done in order for TPC to function? a. Disable the firewall. b. Open the ports used by TPC. c. Use HTTP option in the config properties file. d. Install a Stored and Forward (SnF) agent in the Trusted Zone. 4. During the planning session, the customer listed other IBM products deployed in their environment. Which two products have integration points with TotalStorage Productivity Center V3.1? (Choose two.) a. Tivoli Storage Manager. b. Tivoli Enterprise Console. c. Tivoli Monitoring for Databases. d. Tivoli Monitoring for Applications. e. Tivoli Monitoring for Network Performance. 5. Which command is used to verify that port 80 is not in use before beginning the Agent Manager installation on Windows? a. ports. b. nslookup. c. ipconfig. d. netstat -an.
350
6. When installing TotalStorage Productivity Center V3.1 prerequisite Agent Manager, which database system can be used for the Agent Manager registry database? a. Cloudscape. b. Oracle Database. c. MSSQL Database. d. DB2 Universal Database. 7. What is the proper installation order for installing TotalStorage Productivity Center V3.1 in a Red Hat Enterprise Linux AS V3.0 environment where no previous releases of the product exist, including the prerequisite components? a. Install DB2 UDB Database, TPC V3.1 Server Components, and Agent Manager software. b. Install Agent Manager software, DB2 UDB Database, and TPC V3.1 Server Components. c. Install DB2 UDB Database, and Agent Manager software, and TPC V3.1 Server Components. d. Install TPC V3.1 Server Components, Install Agent Manager software, and DB2 UDB Database. 8. What are the two benefits of deploying the Agent Manager, the DB2 database, and the TotalStorage Productivity Center V3.1 on the same server? (Choose two.) a. The same DB2 and WebSphere software is used. b. Fewer servers will be required for TPC V3.1 deployment. c. No requirements to install WebSphere Application Server separately. d. All TPC V3.1 prerequisites and components share the same server leading to better performance. e. All TPC V3.1 prerequisites and components share the same server leading to better access control.
Appendix B. Sample questions
351
9. How are SAN CIM/OMs manually defined in the TotalStorage Productivity Center V3.1 Server GUI? a. Add the CIM/OM definition through the TPC Server GUI by selecting Administrative Services Discovery CIMOM. b. Add the CIM/OM definition to the Agents/CIMOM subsection through the TPC Server GUI from the Disk Manager section. c. Add the CIM/OM definition to the Discovery/CIMOM subsection through the TPC Server GUI from the Fabric Manager section. d. Add the CIM/OM definition to the Discovery/CIMOM subsection through the TPC Server GUI from the Administrative Services section. 10.What are two ways to add an NAS filter to TotalStorage Productivity Center V3.1 Data Server? (Choose two.) a. Ping. b. Scan. c. Probe. d. Discovery. e. Manual entry. 11.TotalStorage Productivity Center V3.1 has the ability to report on storage devices for availability, usage, and capacity. Which TPC capability is used to collect availability statistics? a. Ping. b. Scan. c. Probe. d. Discovery.
352
12.A request has been submitted to the TotalStorage Productivity Center administrator to reassign a computer from the Accounting group to the Healthcare group. What is the outcome if the computer is added to the Healthcare computer group? a. It will be removed from the Accounting group and will require a new password. b. It will be added to the Healthcare group and will remain in the Accounting group. c. It will be added to both groups simultaneously and then be deleted from the Accounting group. d. It will be removed from the Accounting group before being added to the Healthcare group. 13.The TotalStorage Productivity Center administrator verified with support that they needed to back up the certificate files before making changes. What directory on the Agent Manager will need to be copied to an alternate location? a. /certs. b. /certfiles. c. /certificates. d. /certs-install. 14.Which rule applies when Fabric Manager manages a SAN containing switches from different vendors? a. Zone members must be specified using WWN. b. Zone sets are defined on the highest function switches only. c. Functional capabilities of the SAN become a super-set of the capabilities of the individual switches. d. Fabric Manager will prevent the user from attempting to invoke a zoning function on a switch where it is not supported. 15.A Probe collects data on which of the following? (Choose two.) a. A. files. b. B. groups. c. C. objects. d. D. instance. e. E. directories.
353
16.Scans can collect data on what two types of file system information? (Choose two.) a. LUN capacity. b. Wasted space. c. Computer up-time. d. Percentage of free storage. e. Violations of quotas and constraints. 17.What must have completed before running a Scan with a default database profile? a. Ping. b. Probe. c. Discovery. d. CIM/OM discovery. 18.TotalStorage Productivity Center V3.1 supports forwarding alerts to Tivoli Enterprise Console (TEC) and a SNMP Manager. What two actions are required to enable alert/event forwarding? (Choose two.) a. Specify the trap destination table. b. Install TEC Event Enablement and BAROC files on TPC V3.1 Server. c. Specify the alert notification method on Alert page as SNMP Trap and TEC Event. d. Install the SNMP service with a community name of public and MIB files on TPC V3.1 Server. e. Specify the TEC server and SNMP Manager details using TPC V3.1 GUI (select Administrative Services Configuration Alert Dispositions page. 19.TotalStorage Productivity Center V3.1 supports the concept of Profiles. What is the main purpose in defining a profile? a. To group discovered CIM/OM agents based on the SMI-S compliant profiles returned. b. To represent a set of user-defined objects against which TPC can run monitoring and reporting jobs. c. To specify what statistical information is gathered and to fine-tune and control what resources are scanned during a scan. d. To define limits on a specific resources a user or set of users can use and monitors the usage via thresholds and alerting.
354
20.We highly recommend having separate systems for each CIM/OM agent that needs to be installed. However, the agents can coexist with other applications. What is one of the main reasons for this separation of CIM/OMs? a. To avoid potential performance impact. b. To incorporate fail-over/high-availability architecture. c. To avoid potential subsystem performance data corruption. d. To avoid potential port conflicts between the various CIM/OM vendor software.
355
Answer key
1. B 2. AB 3. B 4. AB 5. D 6. D 7. C 8. AB 9. A 10 DE 11. A 12. D 13. A 14. A 15. CD 16. BE 17. B 18. CE 19. C 20. D
356
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.
IBM Redbooks
For information about ordering these publications, see How to get IBM Redbooks on page 359. Note that some of the documents referenced here may be available in softcopy only. Deployment Guide Series: TotalStorage Productivity Center for Data, SG24-7140 Exploring Storage Management Efficiencies and Provisioning Understanding IBM TotalStorage Productivity Center and IBM TotalStorage Productivity Center with Advanced Provisioning, SG24-6373 IBM System Storage DS6000 Series: Copy Services in Open Environments, SG24-6783 IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774 IBM TotalStorage Productivity Center V2.3: Getting Started, SG24-6490 IBM TotalStorage Productivity Center V3.1: The Next Generation, SG24-7194 ILM Library: Techniques with Tivoli Storage and IBM TotalStorage Products, SG24-7030 An Introduction to Storage Provisioning with Tivoli Provisioning Manager and TotalStorage Productivity Center, REDP-3900 Managing Disk Subsystems using IBM TotalStorage Productivity Center, SG24-7097 IBM TotalStorage Productivity Center for Replication on Windows 2003, SG24-7250 TotalStorage Productivity Center V2.2 Field Installation Guide AKA "The Cookbook", REDP-4037
357
Other publications
These publications are product documentation: IBM TotalStorage Productivity Center for Data for Databases User's Guide, GC32-1730 IBM TotalStorage Productivity Center for Data Installation and Configuration Guide, GC32-1727 IBM TotalStorage Productivity Center for Data Messages, GC32-1731 IBM TotalStorage Productivity Center for Data Quick Reference, GC32-1729 IBM TotalStorage Productivity Center for Data User's Guide, GC32-1728 IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774 IBM TotalStorage Productivity Center Messages, GC32-1776 IBM TotalStorage Productivity Center Problem Determination Guide, GC32-1778 IBM TotalStorage Productivity Center Users Guide, GC32-1775 IBM TotalStorage Productivity Center Workflow Users Guide, SC32-0101
Online resources
These Web sites and URLs are also relevant as further information sources: IBM Redbooks http://www.redbooks.ibm.com/ TotalStorage Productivity Center Version 3 Release 1 Platform Support: Agents, CLI and GUI http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002814 TotalStorage Productivity Center Version 3 Release 1 Platform Support: Managed Database Support http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813 TotalStorage Productivity Center Version 3 Release 1 Supported Product List http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002800
358
TotalStorage Productivity Center Version 3 Release 1: Supported Product 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 support Web site http://www.ibm.com/servers/storage/support/software/tpc
How to get IBM Redbooks

You can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site: ibm.com/redbooks
Help from IBM

IBM Support and downloads ibm.com/support IBM Global Services ibm.com/services
Related publications
359
360
Index
A
Access File Summary report 228 Access Time Summary report 223 adding databases 203 administration tasks 209 administrative authority 84 administrative rights DB2 user 102 Administrative Services 211 administrative services 213 Administrator 70 administrator 44 advanced provisioning 32, 35 Agent install via GUI 76 remote install 76 agent 31, 39 information 218 agent communication ports 165 agent deployment 159 Common Agent logs 174 interactive installation 160 local installation 159 log files 173 run scripts 164 service 172 agent install verification 170 Agent Manager 40 certificates 72 database connection 126 default password 139 default user ID 139 healthcheck utility 125 IBMCDB database 123 installation 83 key file 72 registration port 9511 116 security certificate 120 server installation 139 server port 9511 139 verifying the installation 125 Agent manager public communication port 116 Agent Manager install 84 Agent Manager installation 112 Agent Manager repository 59 Agent Recovery Service 117 Agent Registration password 92, 120 Agent registration password 72 Agent status 219 agentTrust.jks file 72 Alert Disposition 42 alert disposition 179 alert notification 40 Alert statistics 256 Alert Triggering Condition 255 alerting 253 facility 40 alerts 33 notification 40 architecture 33, 35 areas of competency 8 asset information 272 Assets By Storage Subsystem 281 association 256 audit logs 304 automatic filesystem extension 31
B
backup reporting 297 Batch report type 238 batch reports 238 Brocade 199
C
capacity 226 capacity information 287, 292 CD layout 85 centralized repository 58 certificate authority 92 Certificate Authority file 72 certificate authority password 120 certification benefits 3 certificates 7
361
checklist 6 courses 22 Publications 24 role 2 Self study 26 Tivoli Certification 5 chargeback 212 chargeback support 33 CIM Agent troubleshooting 306 CIM/OM 33 CIMOM 39, 50 interoperability namespace 77 manually entering CIMOMs 197 user ID and passwords 196 CIMOM configuration 187 CIMOM discovery alert 189 CIMOM Discovery job 192 CIMOM discovery job 188, 191 CIMOM logins 187 CIMOM logs 199 CIMS format 206 Clients 30 Cloudscape 51 command netstat -an 64 Common Agent logs 174 Common Agent port 63 Common Agent Registration password 165 Common Agent service 172 Common Agent Services 43 Common Internet File System (CIFS) 68 common user errors 308, 311 component installation order 61 component interaction 44 components 85 components and characteristics test 9 comprehensive reporting 33 Computer alerts 256 configuration 86, 157 configuration files 304 configure tracing 217 configuring TotalStorage Productivity Center for Data 157 configuring chargeback chargeback 206 Connection Errors 219
Consecutive Errors 219 constraints 263 Content panel 212 courses 20 create a quota 261 CSV 240 custom install 85 Custom Installation user ID and password rules 87 custom installation 136, 162 customer support 78
D
Data agent monitored databases 60 Data Agent logs 173 Data Agent options 164 Data agent upgrade 175, 313 Data agents supported platforms 55 data flow 35 Data Manager 40 logfile retention 181 My Reports 222 server 37 Data Manager NetWare tree logins 187 Data Server port 9549 138 data server configuration 138 Data Server port 9549 163 Database Migration Utility 60 database reporting 203 database repository 58 database schema 61 database support 33, 58 database-managed space 59 databases IBMCDB 59 DataManager operating 210 DataManager for Chargeback 206 DB2 60 DB2 Administration Server 101 DB2 database performance 132 DB2 database sizing 132 DB2 install 94 DB2 installation 84
362
verify installation 110 DB2 log files 134 DB2 upgrade issue 95 DB2 user account 102 DB2 user IDs 91 DB2 user rights 91 DB2 window services 111 db2level command 110 default database name 59 default installation directory 85 Detail tab 220 Device Server port 9550. 138 Device Server port 9550 163 diagnose the problem 305 direct-attached storage 28 directory alerts 258 directory grouping 246 discontinued functions 50 discovery troubleshooting 310 disk and volume group support 68 disk array subsystems 69 Disk Capacity Summary report 226 Disk Defects report 228 disk space requirements 52 disk/volume group support 68 Domain Name System (DNS) 40 DS4000 33, 195 DS-OPEN-API 195 Duplicate File report 295
extension 31, 67, 268 filesystem alerts 257 filesystems supported 67 filesystems supported 67 free space 226 freespace alert 258 Fully Qualified Host Name 116
G
General Parallel File System (GPFS) 67 General tab 219 Generate Report 225 groups 244 GUI applet 144 GUI for web access 144
H
hardware prerequisites 51 HDS 50 healthcheck utility 125 historical report 291 history aggregator 185 history retention for databases 202 Home Directory tab 151 Host Address 219 Host Name Alias 116 HPQ 50 HP-UX 68 HTTP connection 40
E
e-mail address rules 182 EMC 50 Engenio 50, 199 enterprise repository 3738 Enterprise Storage Server 33, 68 errors 219, 301 Event Integration Facility (EIF) 41 exam discounts 7 Exports or shares 278
I
IBM Publications Center 25 Tivoli Storage Manager 42 IBM AIX V5.3 48 IBM Certified Deployment Professional 8 IBM Enterprise Storage Server 31 IBM Professional Certification mission 2 IBM Professional Certification Program 2 IBM Tivoli Enterprise Console 41 IBM Tivoli Enterprise Console (TEC) 40 IBM Tivoli NetView 41 IBM UDB DB2 204 IBMCDB database 123 IIS Port 8080 150
F
File types report 294 Filesystem 245 filesystem 277 alerts 257
Index
363
information to gather 305 installable components 61, 83 installation 81 agent installation 75 agent locally 76 Agent Manager 83 IBM Tivoli Storage Manager 82 objectives 82 product 81 user ID privileges 69 user IDs 69 installation licenses 128 installation path 85 integration 40 with IBM products 41 with ITSM 31 Internet Information Services 74, 145 itcauser 167
M
magnifying glass 225 MIB 41 Microsoft Cluster Server 40 Cluster Server MSCS 272 Microsoft SQL Server 204 Microsoft Windows domain 71 Monitoring 212 monitoring 244 monitors 33 Most at Risk Files report 230 Most Obsolete Files report 236 multiple condition alert 257 My Reports 212 node 222 My Reports node 222
J
Java applet 153 Java Database Connectivity 38, 58 JDBC 204 job information 221 ping 248 scan 249 job scheduler 3738 JVM heap sizes 312
N
NAS 32 NAS considerations 58 NAS filers 183 NAS support 39, 68, 263 NAS/NetWare 68 NAS/NetWare server entry 184 navigation tree 210 netstat -a 84 netstat command 64 NetView 41 NetWare 39, 187 NetWare servers 57, 183 network appliance 263 connectivity 74 filesystems 67 Network Appliance Filers 68 network filesystems 67 network-attached storage 28 non IBM disk subsystems 50 nslookup 75
K
key file for Agent Manager 72 key files 72
L
Last update 219 licenses 128 log files 173, 199, 302 CLI 144 Device server 144 GUI 144 log-file retention 181 Logical Volume Manager (LVM) 68 logical volumes 277 LUN definition 275
O
Objectives Section 1-Planning 9 Section 5 - Troubleshooting 19 objectives configuration 12 customization and administration 14
364
installation 11 planning 9 product demonstration 15 troubleshooting 19 Oldest Orphaned Files report 236 one server environment 86 online support 78 operating DataManager 210 Operator 70 operator 44 Oracle 51, 60 Oracle SID ID 203 OS user group 247 oslevel command 74 overview 27
Q
quota 182, 236 quotas 182, 261
R
raw volume space 226 RDBMS 203 recommended resources for study 20 Redbooks Web site 359 Contact us xiii Registration Port 116 Report Filter Specification 226 report functions 221 Reporting capacity 287 filesystem capacity 290 Groups 272 historical report 291 reporting facility 270 reports backup 297 standardized 28 subsystem 32 system 222 usage 292 usage violations 297 reserved ports 84 resource history retention 200 resource retention for databases 202 resources for study 20 role based administration 44 role based users 71
P
password rules 91 passwords 87 created during installation 88 pending requests 215 ping job 248 planning 47 Policy Management Archive/Backup 270 Constraints 263 Scheduled Actions 268 policy management 212, 260 quotas 261 policy-based management 31 port requirements 62 ports 44 reserved 84 predefined reports 222 pre-installation tasks 135 prerequisite software 46 prerequisites for certification certification prerequisites 8 privileges 69 probes 241 product documentation 24 profile creation 251 public communication port 9513 139
S
sample test questions 349 SAN File Systems 183 SAN Volume Controller 68 scan agent administration 183 scan job 249 Scan job alerts 257258 Scheduled Actions 268 scheduled actions 268 scheduler 215 scheduler log 216 schema log files 134 schema name 132 scripts 268
Index
365
Secure Port 116 Secure Sockets Layer (SSL) 40 security 6970 considerations 44 security certificates 72 Security Certificates panel 119 server recommendations 61 server recommendations 61 service accounts 7273 service status 215 services 213 shutdown 218 SMI-S 50 SMIS 32 SMI-S Array Reporting 45 SNIA 50 SNIA CTP Certification 45 SNIA Web site 50 SNMP 41 MIB 41 SNMP community 184 software prerequisites 53 SQL Server 51 SQL server 204 srmcp commands 309 standardized reports 28 statistics 252 Storage Access Time report 228 Storage Area Network 48 storage area network 28 Storage Availability report 237 Storage Capacity report 237 Storage Management Initiative Specification 32 Storage Modification Times report 230 storage resource management 28 storage subsystems 68 subsystem reporting 32 summary of changes 48 supported environments 45 supported systems 51 SVC CIM Agent 303 SVC Master Console 190, 195 Sybase 60, 204 System managed (SMS) 132 system reports 222 system requirements 51 system-managed space 59
T
tablespace 202 tape library support 69 TCP/IP ports 62 TEC 40, 180 technical changes 48 test 873 - objectives 9 components and characteristics 9 core requirements 9 objectives 9 prerequisites 8 testing vendors 6 Timezone 219 Tivoli Common Agent 35 Tivoli Common Agent Services 43, 46 Tivoli Storage Manager integration 42 Tivoli Storage Manager integration 31 Topology Viewer 243 Total Free Space report 237 TotalStorage Productivity Center CIMOM configuration 187 component install 127 license 128 TotalStorage Productivity Center for Data architecture 29 Clients 30 Data agent 30 Data manager 30 functions 28 Web server 30 TotalStorage Productivity Center for Disk 35 TotalStorage Productivity Center for Fabric 35 TotalStorage Productivity Center GUI 148 TPC for Data overview 27 TPC superuser 138 TPCDB default database name 59 tpctool 307 trace log files 218 tracing 217 trigger 189 Triggered-actions 259 troubleshooting 301 TSM backup 232 TSM required backup storage 299 TSRMsrv1 user ID 143 two server environment 86
366
typical install 85, 99
U
upgrade data agent 175 usage reporting 292 violations reporting 297 Usage Reporting 292 User grouping 247 user ID rules 91 user IDs 69 user interface 38, 210 user levels 70 User Quota Violations report 236 User Rights Assignments 70 User Space Usage report 237
V
Veritas 68 View Log 216 volume groups 276 volume managers 68
W
Wasted Space report 238 Web server 30 WebSphere Application Server 46, 138 Websphere Application Server IP address 118 Windows Services 72
Index
367
368
(0.5 spine) 0.475<->0.875 250 <-> 459 pages
Back cover
Certification Study Guide: IBM TotalStorage Productivity Center for Data V3.1
Prepare for certification in theory and practice Gain practical experience with the provided examples and tips Contains a hands-on lab and sample test
This IBM Redbook is a study guide for IBM TotalStorage Productivity Center for Data Version 3.1, and it is targeted for professionals who want to get an IBM Certification in this specific product. This Certification, offered through the Professional Certification Program from IBM, is designed to validate the skills required of technical professionals who work in the implementation of the IBM TotalStorage Productivity Center for Data Version 3.1 product. This IBM Redbook provides a combination of theory and practical experiences necessary for a general understanding of the subject matter. It also provides sample questions that will help in the evaluation of personal progress and provide familiarity with the types of questions that will be encountered in the exam. This IBM Redbook does not replace practical experience, nor is it designed to be a stand-alone guide for any subject. Instead, it is an effective tool that, when combined with education activities and experience, can be a useful preparation guide for the exam.
INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION
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.
For more information: ibm.com/redbooks

SG24-7390-00 ISBN 0738489808

Certification Study Guide IBM Total Storage Productivity Center V3.1 - Sg247390

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Certification Study Guide IBM Total Storage Productivity Center V3.1 - Sg247390

Загружено:

Авторское право:

Доступные форматы

Front cover

Carlos Jos Otlora Yepes Bart Jacob

Copyright IBM Corp. 2007. All rights reserved.